Skip to content
jsmanifest logojsmanifest

MCP Server Config Generator

Configure a Model Context Protocol server once and export the exact JSON for Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf. Runs entirely in your browser — nothing is uploaded anywhere.

  • Free · no signup
  • 5 clients, one form
  • Runs 100% in your browser
servers0

Add a server or pick a popular one, and the config for every MCP client appears on the right.

claude_desktop_config.json
{
  "mcpServers": {}
}
3 lines

File: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Then: Fully quit and reopen Claude Desktop (a window close is not enough).

One MCP config, every AI client

The Model Context Protocol (MCP) is the open standard that connects AI assistants to your tools, files, and APIs. Every client reads a small JSON config to know which servers to launch — but the shape of that JSON is annoyingly different from one client to the next, and a single wrong key silently breaks the connection.

This free tool fixes that. Describe each server once — a local stdio command or a remote HTTP endpoint — then flip between Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf to get the exact, copy-paste-ready config for each. It handles the differences for you: mcpServers versus servers, url versus serverUrl, the required type fields, and VS Code’s inputs array for secrets.

How it works

  1. 1

    Add one or more MCP servers on the left — either pick a popular preset (filesystem, GitHub, Postgres, memory, git, fetch…) or add your own. Everything runs locally in your browser; nothing is uploaded.

  2. 2

    For a local server choose the "stdio" transport and set its command, arguments, and environment variables. For a hosted server choose "Remote (HTTP)" and paste the URL plus any auth headers.

  3. 3

    Pick your client — Claude Desktop, Claude Code, Cursor, VS Code, or Windsurf — and the JSON instantly reshapes to that client’s exact format (the right top-level key, the right URL field, and required type fields).

  4. 4

    Copy the config or download it with the correct filename, then drop it into the file path shown beneath the output and restart the client. Use “Share” to hand the whole setup to a teammate as a link.

Frequently asked questions

What is an MCP server config?

The Model Context Protocol (MCP) is an open standard that lets AI clients like Claude, Cursor, and VS Code connect to external tools and data sources. Each server is declared in a small JSON config file that tells the client how to launch a local process (stdio) or reach a hosted endpoint (HTTP). This tool builds that JSON for you and tailors it to each client’s exact shape.

Why does the JSON differ between clients?

The core fields are similar, but the wrappers differ. Claude Desktop, Claude Code, Cursor, and Windsurf put servers under a top-level "mcpServers" key, while VS Code uses "servers". VS Code also requires a "type" field on every server and lifts secrets into a separate "inputs" array. Claude Code requires "type": "http" on remote servers, and Windsurf names the remote endpoint "serverUrl" instead of "url". This generator applies the right rules automatically so you don’t have to remember them.

Where do I put the generated file?

It depends on the client. Claude Desktop uses claude_desktop_config.json in its app-support folder; Claude Code reads .mcp.json from your project root; Cursor uses .cursor/mcp.json; VS Code uses .vscode/mcp.json; and Windsurf uses ~/.codeium/windsurf/mcp_config.json. The exact path (and how to reload the client) is shown right under the generated output for whichever client you select.

How do I add a local (stdio) versus a remote (HTTP) server?

A stdio server runs on your machine as a child process — you give it a command (like npx or uvx), arguments, and optional environment variables. A remote server is already hosted somewhere, so you give it a URL and any authentication headers (for example an Authorization: Bearer token). Toggle "Local (stdio)" or "Remote (HTTP)" on each server card and the generator emits the correct fields.

How are API keys and tokens handled?

For VS Code, any environment variable or header whose name looks sensitive (token, api key, password, Authorization, …) is automatically lifted into VS Code’s "inputs" array and referenced as ${input:id}, so the client prompts for it instead of hard-coding the secret in the file. Other clients keep the literal value you entered. Either way, nothing you type is sent anywhere — the config is generated entirely in your browser.

Is my configuration uploaded anywhere?

No. The generator runs entirely client-side. Server names, commands, URLs, and tokens never leave your device — the JSON is built locally and copied or downloaded directly. The optional "Share" link encodes the setup into the URL fragment, which is only sent to whoever you give the link to.

Which MCP servers can I add?

Any of them. The presets cover popular official servers — filesystem, GitHub (hosted), memory, sequential-thinking, git, fetch, time, PostgreSQL, and the "everything" demo server — but you can add a custom server with any command, args, env, URL, or headers. The presets are just a fast starting point you can edit.

More developer tools

Setting up an AI coding environment? Pair this with the CLAUDE.md / AGENTS.md generator, browse the full set of free, browser-based developer tools from jsmanifest, or read the latest JavaScript and TypeScript articles.