Free · no signup · browser-local

MCP Config Generator for Claude Desktop, Cursor and VS Code

Choose a supported client and transport, enter command arguments or a server URL, and export client-specific MCP JSON without executing or connecting.

Browse all tools →

Local document tools · no commands run · no endpoint requests

Build your MCP config

Add up to 50 servers. Only checked servers are exported; only fields for the selected transport enter the output.

Server 1
Supported scope

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.

1 / 1 servers selected

Your JSON output

claude_desktop_config.json

Getting started

Choose a client and supported transport, enter the command with JSON-array arguments or an HTTP(S) URL, then download.

Before you use the result

A conservative subset is supported. Desktop export covers local stdio; Cursor URL connections and VS Code HTTP are supported. No server is contacted.

Try an example

Generate a VS Code servers entry with type http and https://example.com/mcp.

How it works

Local checks enforce client root keys, transport fields, argument arrays and URL rules; official references were checked on 2026-11-03.

Frequently asked questions

Build client-specific MCP JSON for Claude Desktop, Cursor or VS Code without running commands.

How do I use MCP Config Builder?

Choose a client and supported transport, enter the command with JSON-array arguments or an HTTP(S) URL, then download.

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?

A conservative subset is supported. Desktop export covers local stdio; Cursor URL connections and VS Code HTTP are supported. No server is contacted.