Skip to content

MCP server 'blocked by policy' #3934

Description

@mydeveloperplanet

Describe the bug

We have a custom MCP registry which is checked when local MCP servers are configured. Although the local MCP configuration is correct and works just fine within VSCode and IntelliJ plugin, an error message 'MCP server is blocked by policy' is shown.

It is unclear what causes this. The process log mentions the following:

2026-06-25T11:40:36.761Z [ERROR] MCP server "io.github.sooperset/mcp-atlassian" filtered: Server "io.github.sooperset/mcp-atlassian" found in registry <REDACTED> but local configuration does not match the registered server identity

Affected version

GitHub Copilot CLI 1.0.65

Steps to reproduce the behavior

  1. Configure an MCP server in the mcp-config.json in the ~/.copilot directory or just install it from within the Copilot CLI with /mcp add
  2. The MCP server is blocked

Expected behavior

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:enterpriseGitHub Enterprise (GHE/GHES) support, org policies, and enterprise settingsarea:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registry

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions