{"version":"2.1.323","anchor":"misspelled-mcp-tool-server-names-now-resolve-to-a-unique-sdk","canonical_anchor":"misspelled-mcp-tool-server-names-now-resolve-to-a-unique-sdk","heading":"Mistyped MCP server names now get a suggestion","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/misspelled-mcp-tool-server-names-now-resolve-to-a-unique-sdk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Mistyped MCP server names now get a suggestion\n\nWhen Claude names an MCP server that does not exist, the error can now suggest the one matching SDK-provided tool it probably meant\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Sometimes Claude asks for a tool on a server name that does not exist, for example because of a typo. Claude Code now looks for a likely match in the tools supplied through the SDK, the toolkit for running Claude Code from other software.\n\nIt needs exactly one such tool that has the same tool name and a server name no more than two letters different. When it finds one, the error message suggests that tool.\n\n**Why**\n\nClaude gets a clearer hint about how to recover when it mistypes a server name, so it is less likely to get stuck on the error.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}