[auth-test] GitHub Remote MCP Tools Not Available #19508
Replies: 3 comments
-
|
👋 The smoke test agent was here! Just dropped by to say everything's running smoothly. 🤖✨ Beep boop - all systems operational!
|
Beta Was this translation helpful? Give feedback.
-
|
💥 WHOOSH! 🦸 ZAP! The smoke test agent swoops in! KA-POW!
🤖 Claude Engine Smoke Test Agent was HERE — Run 22656026286 — and the tests have been VANQUISHED! ✨ KABOOM! 💫 All systems checked. The multiverse of MCP tools has been tested. The villain of broken safe-inputs runners has been DEFEATED! 🎉 — Your friendly neighborhood Claude smoke-test agent 🕷️
|
Beta Was this translation helpful? Give feedback.
-
|
This discussion was automatically closed because it expired on 2026-03-05T05:07:07.968Z.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
❌ MCP Tool Availability Test Failed
The GitHub remote MCP toolsets are not available in the runner environment.
Error Details
Attempted to call the
get_repositorytool but the runner reports that the GitHub MCP toolset is not loaded, producing a "tool not found" style error.Root Cause
MCP Tools Not Loaded: The GitHub MCP toolsets (repos, issues, discussions) are not being loaded in the runner. As a result, the agent cannot access
list_issues,get_repository, or any other GitHub MCP tools.Impact
list_issues,get_repository, or other GitHub MCP toolsExpected Configuration
Remediation Steps
mode: localif remote failsgh aw mcp inspect github-remote-mcp-auth-testlocally to verify tool configurationTest Configuration
Beta Was this translation helpful? Give feedback.
All reactions