{"version":"2.1.239","anchor":"the-word-mcp-in-an-argument-no-longer-looks-like-the-mcp-sub","canonical_anchor":"the-word-mcp-in-an-argument-no-longer-looks-like-the-mcp-sub","heading":"The word \"mcp\" in an argument no longer looks like the mcp subcommand","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/the-word-mcp-in-an-argument-no-longer-looks-like-the-mcp-sub","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### The word \"mcp\" in an argument no longer looks like the mcp subcommand\n\nPassing the word \"mcp\" as an argument no longer makes Claude Code think it should run as an MCP server.\n\n**What**\n\nThe check for whether Claude Code is running as an MCP server now asks which subcommand was actually parsed instead of scanning the raw command line for the word.\n\n**Details**\n\n- An unrelated argument or file path containing \"mcp\" previously matched and suppressed a runtime override.\n\n**Evidence**\n\n`process.argv.includes(\"mcp\")`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}