Claude Desktop MCP Not Showing on Windows: Causes and Fixes

On Windows, Claude Desktop reads MCP servers from one file:%APPDATA%\Claude\claude_desktop_config.json, with a top-level mcpServers object. That file covers local stdio servers only — remote MCP servers are added through Settings > Connectors, a UI flow with OAuth sign-in, never as a URL entry in the JSON. When a server does not show up, the file usually failed to parse, the app was never fully restarted, or the server process failed to launch.

Symptoms this page covers

• Every server vanished from the tools list at once after an edit.
• A newly added server never appears, despite a “correct-looking” config.
• A remote MCP server added to the JSON does nothing.
• The config works on a colleague’s Mac but not on your Windows machine.

Possible causes, ordered by evidence strength

1. Unescaped Windows backslashes (provable statically). JSON strings treat\ as an escape character, and a path likeC:\path\mcp\npx.cmd fails in two distinct ways. Sequences such as\p or \m areinvalid JSON escapes — the file cannot be parsed at all, so every server disappears. Sequences such as \t or \n arevalid escapes — the file parses, but the path silently becomes a tab or newline character and the command no longer exists. Use forward slashes (C:/path/mcp/npx.cmd) or double every backslash (C:\\path\\mcp\\npx.cmd).
2. A remote URL entry in the JSON (provable statically). Claude Desktop does not read remote servers from claude_desktop_config.json. Aurl entry is a blocking schema error, not a remote config — remote servers go through Settings > Connectors.
3. Editing the wrong file or location (verifiable on disk). The file must be exactly%APPDATA%\Claude\claude_desktop_config.json — the Claude folder inside roaming app data, with that exact filename. Aclaude_desktop_config.json saved anywhere else is never read.
4. The app was not fully restarted (version-dependent). Claude Desktop reads the config at startup. Closing the window may not quit the app; on Windows, quitting from the system-tray icon is the reliable full exit in current versions. Menu wording and tray behavior change between versions, so the stable principle is: make sure the process fully exits, then relaunch.
5. The server process failed to launch (visible in logs). A config can be perfectly valid while the launch fails — classically spawn npx ENOENT, because a GUI app does not inherit the PATH your terminal uses. That is a runtime problem; see thespawn ENOENT / npx not found guide.

Broken example: backslashes that break JSON

{"mcpServers":{"fs":{"command":"C:\path\mcp\npx.cmd","args":["-y","pkg"]}}}

Counter-example: a remote URL entry

{
  "mcpServers": {
    "api": {
      "url": "https://mcp.example.com/v1"
    }
  }
}

The corrected config (local stdio)

This is the exact output of this site’s generator for Claude Desktop on Windows: top-levelmcpServers, a local stdio entry withcommand and args, and no URL fields. Save it to%APPDATA%\Claude\claude_desktop_config.json.

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ]
    }
  }
}

How to fix it

1. Fully quit Claude Desktop (in current versions: quit from the system-tray icon — closing the window is not enough; this behavior is version-dependent, so confirm the process is gone).
2. Open %APPDATA%\Claude\claude_desktop_config.json in a text editor.
3. Fix the JSON: forward slashes or doubled backslashes in Windows paths, no trailing commas, no comments.
4. Move any url entries out of the file — add remote servers via Settings > Connectors instead.
5. Validate the edited file with the MCP Config Doctor (client: Claude Desktop, OS: Windows) before relaunching.
6. Relaunch the app and check a new chat for the server’s tools.

Verify inside Claude Desktop

• The server’s tools appear in a new chat (the tools/hammer indicator in current versions — icon placement is version-dependent; the stable signal is that the server’s tools are callable).
• The app’s own MCP logs (opened from the developer settings in current versions) show no parse error and no spawn ENOENT.
• Editing the config and relaunching produces a visible change; if nothing changes, the app never re-read the file — revisit the full-restart step.

What static checks cannot prove

A valid claude_desktop_config.json proves only that the text is parseable and matches the Claude Desktop schema you checked it against — it does not prove the app has read or registered your servers. Whether the file sits at the path Claude Desktop actually reads, and whether the running instance has loaded it, can only be confirmed inside the app (the tools list and the MCP logs above). It also cannot prove the server binary exists on the PATH Claude Desktop inherits, that tokens are valid, or that the server starts without crashing. Menu names, tray behavior, and log locations also drift between versions — the version-independent rules are: valid JSON, stdio-only entries, a full restart, and a log check.

Official sources

• Claude support: getting started with local MCP servers on Claude Desktop— the config file and local stdio entries (search_snippet verification).
• Claude support: custom connectors using remote MCP— the Settings > Connectors flow for remote servers (search_snippet verification).

Frequently asked questions

Setting up Claude Desktop from scratch, including macOS paths? Read theClaude Desktop MCP config guide. Server dies at launch with spawn ENOENT? Seespawn ENOENT / npx not found. Comparing formats across clients? Check theMCP client compatibility matrix.