Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 26, 2026

GitHub Remote MCP auth-test fails when toolsets aren't loaded in the runner environment, producing "tool not found" errors misclassified as authentication failures. No preflight verification exists before agent execution.

Changes

Preflight check script (check_github_remote_mcp_toolsets.sh)

  • Sends MCP tools/list request to verify toolset availability
  • Distinguishes auth failures (401/403) from missing toolsets (empty tools list)
  • Exit codes: 0=available, 1=unavailable, 2=skip (local mode/not configured)
  • Provides context-specific remediation steps

Gateway startup integration (start_mcp_gateway.sh)

  • Invokes preflight check after connectivity validation
  • Graceful degradation: logs warning on toolset unavailability, continues execution
  • Delegates missing tool handling to agent via safe-outputs reporting

Test coverage (check_github_remote_mcp_toolsets_test.sh)

  • Validates argument handling, config parsing, mode detection, URL filtering

Behavior

Toolsets unavailable:

ERROR: GitHub Remote MCP returned empty tools list

Root Cause:
  The GitHub MCP toolsets (repos, issues, discussions, etc.) are not available.
  This is not an authentication issue - the server is reachable but the
  tools themselves are not loaded.

Remediation:
  1. Verify GitHub Copilot MCP service status
  2. Check if the toolsets feature is enabled for your GitHub organization
  3. Consider using local mode (mode: local) as a fallback

Workflow continues, agent detects missing tools and creates safe-outputs discussion with diagnostic context.

Original prompt

This section details on the original issue you should resolve

<issue_title>[deep-report] Harden GitHub Remote MCP auth-test by ensuring toolsets load or fallback to local mode</issue_title>
<issue_description>### Description
The GitHub Remote MCP auth-test continues to fail because GitHub MCP toolsets are not loaded in the runner (tools missing, not auth failures). Add a preflight check to verify tool availability, and implement a documented fallback (e.g., switch to local mode or emit an actionable error with remediation) when remote toolsets are unavailable.

Expected Impact

Reduces false-negative auth-test failures and improves signal on actual MCP availability issues.

Suggested Agent

workflow-analysis or mcp-analysis agent

Estimated Effort

Medium (1-4 hours)

Data Source

DeepReport Intelligence Briefing 2026-01-26; auth-test discussion §21356644658

AI generated by DeepReport - Intelligence Gathering Agent

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI and others added 4 commits January 26, 2026 16:07
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
…dd security comments

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Add preflight check for GitHub Remote MCP auth-test Add GitHub Remote MCP toolsets preflight check with graceful degradation Jan 26, 2026
Copilot AI requested a review from pelikhan January 26, 2026 16:16
@pelikhan pelikhan closed this Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[deep-report] Harden GitHub Remote MCP auth-test by ensuring toolsets load or fallback to local mode

2 participants