{"version":"2.1.305","anchor":"mcp-tool-name-schema-loosened","canonical_anchor":"mcp-tool-name-schema-loosened","heading":"MCP tool names with only a server part now pass a validation check","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/mcp-tool-name-schema-loosened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### MCP tool names with only a server part now pass a validation check\n\nA check on MCP tool names now accepts `mcp__server` on its own, not only the full `mcp__server__tool` form\n\n**Unclear.** It is not clear which setting or field this name check applies to.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools, and their tools are named like `mcp__server__tool`. One check on these names used to require both the server and the tool part. It now accepts any name starting with `mcp__`, so `mcp__server` on its own passes.\n\n**Why**\n\nWherever this check applies, you can now refer to a whole MCP server at once instead of one tool at a time.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}