Local diagnostic tool · 本地诊断

Stop guessing why your MCP config fails.

Paste JSON or Codex TOML. Get exact, actionable diagnostics for wrapper names, transports, arguments, URLs and exposed credentials—then convert the working config to another client.

粘贴 MCP 配置,定位格式与安全问题,并在 Claude、Cursor、VS Code、Codex、Gemini CLI 之间转换。数据不离开浏览器。

  • 6 clients
  • JSON ↔ TOML
  • Secret leak warnings
  • No signup
  • No upload

1. Paste configuration

Processed only in this tab. Do not paste live secrets into any website.

2. Corrected conversion


            

.mcp.json

ReadyNothing leaves this browser
  • Paste a config and run the doctor.

Build a clean MCP config from scratch

No existing file? Enter one server below. Put each command argument on its own line so spaces inside paths and values are preserved. For credentials, reference an environment variable instead of inserting the real token.

One protocol, several incompatible config shapes

MCP standardizes how clients talk to servers; it does not standardize every application's local settings file. Copying a valid snippet into the wrong wrapper or filename is one of the most common setup failures.

ClientProject configTop-level shapeRemote HTTP fieldWhat this tool handles
Claude Code.mcp.jsonmcpServerstype: "http" + urlValidate + convert
Claude DesktopUser app configmcpServersurlValidate + convert
Cursor.cursor/mcp.jsonmcpServersurlValidate + convert
VS Code.vscode/mcp.jsonserverstype: "http" + urlValidate + convert
Codex.codex/config.toml[mcp_servers.name]url = "…"TOML + JSON conversion
Gemini CLI.gemini/settings.jsonmcpServershttpUrlValidate + convert

What the doctor checks

CHECK 01

Parser failures

Invalid JSON, smart quotes, Windows backslash escapes, trailing commas and a practical subset of Codex MCP TOML.

CHECK 02

Client wrapper mismatch

Detects the servers versus mcpServers problem and converts to the selected client's structure.

CHECK 03

Transport conflicts

Flags definitions that combine command and url, malformed URLs, insecure remote HTTP and legacy SSE.

CHECK 04

Wrong value types

Finds comma-separated argument strings, non-object environment blocks and incomplete server definitions.

CHECK 05

Credential exposure

Warns when token, key, password or authorization fields appear to contain literal credentials rather than variable references.

CHECK 06

Startup friction

Catches easy-to-miss issues such as interactive npx installation prompts and Claude Code's reserved workspace server name.

How to troubleshoot after the file validates

STARTUP

Run the command directly

Copy the command and arguments into a terminal. Package-not-found, permission and runtime errors happen before MCP negotiation and cannot be fixed by changing the JSON wrapper.

STATUS

Use the client's MCP view

Claude Code exposes /mcp and claude mcp list; Codex exposes /mcp and codex mcp list; Gemini CLI exposes /mcp and gemini mcp list.

LOGS

Separate config from connection

A structurally valid file can still fail because the executable is absent, the URL is unreachable, OAuth is incomplete, the working directory is wrong or the server writes logs to stdout.

Specification sources and scope

This tool's client mappings were checked against first-party documentation on July 31, 2026. It validates configuration structure; it does not execute an untrusted MCP server or claim that a remote endpoint is reachable.

MCP config FAQ

Related AI agent tools