MCP Configuration
Malformed .mcp.json breaks all servers
A JSON syntax error anywhere in .mcp.json can prevent the whole file from parsing, taking every server in it down at once, not just a specific entry.
Because .mcp.json is a single JSON document, an invalid file doesn't fail gracefully per-server — it fails to parse at all, and every server that would have been defined in it simply isn't loaded.
This is worth ruling out first whenever multiple, previously-working servers all go missing at once, especially right after a manual edit to the file — a missing comma or an extra trailing one is enough.
Running the file through any JSON validator is a faster first check than reasoning about it by eye, particularly in a large config with several servers defined.
Validate .mcp.json with any JSON linter before assuming a specific server is the problemFrequently asked questions
What does Malformed .mcp.json breaks all servers do in Claude Code?
A JSON syntax error anywhere in .mcp.json can prevent the whole file from parsing, taking every server in it down at once, not just a specific entry.
How do I use it?
Try: Validate .mcp.json with any JSON linter before assuming a specific server is the problem
Any caveats to know about?
Running the file through any JSON validator is a faster first check than reasoning about it by eye, particularly in a large config with several servers defined.
Is this covered in OG Flow Code Premium Toolkit?
Yes — Malformed .mcp.json breaks all servers and patterns like it are covered by the commands, and in higher tiers the specialist agents and guided skills, in OG Flow Code Premium Toolkit. Tiers start at $19.90.
Want the full command, hook, and template pack?
This is one pattern from the OG Flow Code toolkit. Choose the tier that fits your workflow, including Multi-Stack for six additional language stacks.
See pricing — from $19.90 once