{"version":"2.1.300","anchor":"managed-mcp-entry-validation-codes-and-ccs-repo-rules-featur","canonical_anchor":"managed-mcp-entry-validation-codes-and-ccs-repo-rules-featur","heading":"New checks for MCP server entries and a new repo rules entry","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/managed-mcp-entry-validation-codes-and-ccs-repo-rules-featur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### New checks for MCP server entries and a new repo rules entry\n\nClaude Code adds codes for MCP server entries with no transport or malformed OAuth scopes, and a new `ccs_repo_rules` entry\n\n**Unclear.** Whether these codes are shown to you when an MCP server entry is rejected is not clear.\n\n**What**\n\nMCP servers are outside programs that add tools to Claude Code. Claude Code now has new codes for problems in an MCP server entry:\n\n- `MCP_ENTRY_TRANSPORT_MISSING`: the entry does not say how to connect to the server.\n\n- `MCP_ENTRY_OAUTH_SCOPES_LIST`: a problem with the list of OAuth scopes, the permissions the server asks for at sign-in.\n\n- `MCP_ENTRY_OAUTH_SCALAR`: a problem with a single OAuth value.\n\nA `ccs_repo_rules` entry was added next to other repository-related entries, and a `ccr_upload_stream` entry was removed from a nearby list.\n\n**Why**\n\nThese point to checks on MCP server settings set by an organization, and to syncing repository rules.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}