Claude Desktop MCP Config Path Doctor
Find the MCP config file Claude Desktop is likely reading before you edit JSON, restart the app, or review a local server install. This page runs locally in the browser and does not ask you to paste config contents.
Why this exists
- 1Path mismatchWindows MSIX installs can leave users editing one config while Claude reads another path.
- 2Silent failureThe symptom can look like valid JSON with no MCP icon, no tools, and no useful log.
- 3Safe next stepAfter the path is right, review the redacted config before approving local execution.
Build a path checklist
Do not paste live credentials, customer records, private endpoints, payment data, private handles, full names, private screenshots, or full transaction identifiers into public issues or buyer intake.
Local checklist
Source-backed problem
Windows MSIX virtualized path
GitHub issue showing a wrong-file Edit Config path and the virtualized Windows path workaround.
Claude Desktop MCP help
Official help for checking connected local MCP servers, extension logs, and sensitive configuration handling.
Claude Code MCP docs
Official docs for importing Claude Desktop MCP servers and keeping Claude Code config separate.
After the path is right
- Paste only a redacted copy into the MCP Config Risk Reviewer to flag local execution, package runner, broad path, remote URL, and sensitive env-key risks.
- After the server connects, use the tools/list importer to review added or changed tools before first use.
- For a paid second pass, use the scoped checkout path only after the MCP config or tools/list surface can be described without private data.