Ultra hard mode: the config file, the LLM merge rule, and star/fork trust
One misplaced comma and Claude Desktop stops loading every server you own. So you never type in that file - you let a model merge it.
claude_desktop_config.json is a list of installed servers, each with a name and a run command in a syntax 'Node.js can understand' (npx). Reached via Settings > Developer > Edit Config. It is the gateway to mcp.so's 17,433 servers and to any server you build. The safety rule for non-developers: paste the current config and the new server's snippet into Perplexity/ChatGPT/Claude/Gemini, ask it to merge, paste the result back, save, restart Claude, test. Vetting: 'visit server' -> GitHub stars and forks - Firecrawl's 5,300 stars / 588 forks is trusted; 5-10 is a risk; some servers also need API keys from the tool's own site. Demo installed MCP Advisor, a server that recommends other servers.
Paul already lives in this file for Desktop Commander and friends; the merge-by-LLM rule is the one that prevents the outage.
Go deeper
In one line: Manual config editing = access to every MCP server incl. your own; merge configs with an LLM, never by hand; trust by stars/forks; restart after saving.
Four tiers: easy / medium (~30) / hard (Smithery ~3,000) / ultra hard (mcp.so 17,433+) (l3186070 0:35-0:37)
Settings > Developer > Edit Config opens claude_desktop_config.json (l3186070 0:46-0:47)
Never hand-edit; LLM merges old + new config (l3186070 0:58)
Vet by GitHub stars/forks via 'visit server' (l3186070 0:56)
Recipe: pick server -> copy config -> check trust -> merge -> paste -> save -> restart -> test (l3186070 1:01)
▶ Watch this taught:









