{"version":"2.1.299","anchor":"blank-project-mcpjson-is-read-as-no-servers","canonical_anchor":"blank-project-mcpjson-is-read-as-no-servers","heading":"An empty project .mcp.json no longer causes a config error","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/blank-project-mcpjson-is-read-as-no-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### An empty project .mcp.json no longer causes a config error\n\nA project `.mcp.json` file that is empty or holds only spaces is now read as listing no MCP servers, with no error\n\n**What**\n\nA project's `.mcp.json` file lists MCP servers, which are outside programs that give Claude Code extra tools. If that file is blank or contains only spaces and line breaks, Claude Code now treats it as listing no servers. It no longer tries to read it as JSON and fail. A note saying the file was blank is written to the debug log.\n\n**Why**\n\nAn empty `.mcp.json` no longer shows a configuration error. You can leave the file in place with nothing in it.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}