Failed to fetch MCP registry policy for individual user (404)

[pingrilin94-svg]

Describe the bug

I am using Copilot Pro (individual plan) and have already enabled MCP server usage in the web settings.

Today when I opened Copilot CLI and resumed a previous session, I got the following error:

2 MCP servers were blocked by policy

When I created a new session, the same error occurred.

I then updated Copilot CLI to the latest version (v1.0.15), but the issue persisted in new sessions.

After some time, creating a new session no longer triggered the error, but resuming old sessions still consistently produced the same error.

The underlying error appears to be a failed request to the MCP registry policy endpoint:

Request to MCP registry policy at https://api.github.com/copilot/mcp_registry failed with status 404

This suggests that MCP registry policy may not be available or incorrectly configured for individual users.

Affected version

GitHub Copilot CLI 1.0.15.

Steps to reproduce the behavior

1. Use Copilot Pro (individual account)
2. Enable MCP server feature in Copilot web settings
3. Open Copilot CLI
4. Resume an existing session
   → Observe error: MCP servers were blocked by policy
5. Create a new session
   → Initially same error occurs
6. Update Copilot CLI to latest version (v1.0.15)
7. Create a new session again
   → Eventually no error
8. Resume old session
   → Error persists

Expected behavior

I could not find any way for individual users (Copilot Pro) to configure or define an MCP registry policy. Perhaps it should not be fetched for individual users, and no servers should be blocked as a result.

Additional context

2026-04-02T10:18:12.220Z [DEBUG] No MCP config loaded from ODR (ODR unavailable or returned no usable servers)
2026-04-02T10:18:12.223Z [DEBUG] Sending telemetry event: copilot-cli/cli.telemetry (kind: mcp_policy_check)
2026-04-02T10:18:12.275Z [DEBUG] No MCP host available for GitHub configuration
2026-04-02T10:18:12.328Z [INFO] No update needed, current version is 1.0.15, fetched latest release is v1.0.15
2026-04-02T10:18:12.721Z [ERROR] Request to MCP registry policy at https://api.github.com/copilot/mcp_registry failed with status 404 (request ID: A43E:27590E:876D02:9A9ED7:69CE4264), body: {"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}
2026-04-02T10:18:12.722Z [WARNING] Failed to fetch MCP registry policy: GitHubApiError: Failed to fetch MCP registry policy: 404 Not Found. Non-default MCP servers will be blocked until the policy can be fetched.
2026-04-02T10:18:12.724Z [ERROR] MCP server "query" filtered: Could not verify server against any configured registry
2026-04-02T10:18:12.724Z [ERROR] MCP server "chrome-devtools" filtered: Could not verify server against any configured registry

[binhex]

I'm seeing this for v1.0.14 and v1.0.15 both show this bug, v1.0.13 works as expected.

[zeroamps]

I'm seeing this for v1.0.14 and v1.0.15 both show this bug, v1.0.13 works as expected.

Can confirm "for v1.0.14 and v1.0.15 both show this bug, v1.0.13 works as expected"

[Muchaszewski]

Can confirm, using /new about 20 times removed the policy error for me. But the underlying MCP are still unavailable even though the message no longer shows up.

[ghighi3f]

I'm in the same boat, Copilot Pro individual, after last update to 1.0.15 I get 1 MCP servers were blocked by policy.
The policy check shouldn't block Pro users since the endpoint returns 404 for them.

[szgergo]

Same issue here. Copilot Pro+ (personal), CLI v1.0.15, macOS.

I dug into the CLI source (app.js) and found the chain of events:

1. There's a feature flag copilot_cli_mcp_allowlist that gates an org registry check
2. CLI calls GET /copilot/mcp_registry — returns 404 for individual plans
3. The catch block goes fail-closed: all non-default MCP servers get blocked

What's interesting in my case: I'm a member of a few orgs I created for open source projects. Copilot is not enabled on any of them — I've never configured it. But gh api /orgs/<my-org>/copilot/billing returns a phantom plan_type: "business" with 0 seats and everything set to "unconfigured". I suspect the CLI sees these and tries to enforce registry policies that don't exist.

Weirdly, the same context7 server works fine in:

• Copilot Chat extension in IntelliJ IDEA (starts normally, tools exposed)
• Copilot CLI from VS Code's terminal (even resuming the same session works, all MCP servers load)

But in IntelliJ IDEA's terminal, the CLI blocks it — even for the same session that works from VS Code. One more thing: in VS Code's terminal, the default shell is zsh, but as soon as I start copilot it switches to bash. Not sure if that's related but worth noting. copilot --resume <session-id> works fine with MCP servers loaded. But if I start a fresh copilot, then /resume, then pick the session by name — MCP servers get blocked. Same session, different resume path, different result.

I also confirmed that GITHUB_COPILOT_3P_MCP_ENABLED=true passes the first check (the code does === "true" strict comparison), but the registry fetch failure downstream still blocks everything.

env:

• CLI 1.0.15, macOS 26.4 (arm64)
• Copilot Pro+ (api.individual.githubcopilot.com)
• Orgs with phantom Business plans, Copilot never enabled on them