Free · no signup · browser-local
MCP Config Converter for Cursor, VS Code and Desktop
Convert the supported MCP configuration subset between clients. Inspect precise compatibility issues without silently dropping unknown settings or running servers.
Local document tools · no commands run · no endpoint requests
Convert MCP client format
Strict JSON only: 100 KB, depth 20, 5,000 nodes and 1–50 servers. stdio: command, args, env. Remote: url and string headers. Desktop uses local mcpServers; Cursor uses mcpServers and URL negotiation; VS Code uses servers with explicit type stdio/http.
Unknown fields (inputs, auth/oauth, envFile, cwd, sandbox, SSE type and others) block output. They may be valid client features. Cross-client variable expressions and numeric/null env values are blocked when semantics cannot be preserved. No connection or authentication is verified.
Conversion and merge exports retain your values and may contain credentials. Review them before sharing. The diff report masks values by default.
Your JSON output
mcp.jsonGetting started
Choose the source and target client, paste or import strict JSON, resolve field issues, then copy or download the actual configuration.
Before you use the result
Only the documented basic subset is converted. Desktop output is local stdio JSON; unknown fields and unsafe cross-client interpolation block output. No server is contacted.
Try an example
Convert a multi-server Claude Desktop mcpServers file to VS Code servers with explicit stdio types.
How it works
A bounded local parser checks every field before mapping client root keys and transport syntax. Unsupported options are reported at their JSON paths instead of silently removed.
Frequently asked questions
Convert MCP JSON between Claude Desktop, Cursor and VS Code with explicit checks for fields that cannot be preserved.
How do I use MCP Config Converter?
Choose the source and target client, paste or import strict JSON, resolve field issues, then copy or download the actual configuration.
Does this tool upload my data?
Inputs and files are processed in your browser. Page-view analytics do not contain your tool input.
What should I check before using the result?
Only the documented basic subset is converted. Desktop output is local stdio JSON; unknown fields and unsafe cross-client interpolation block output. No server is contacted.