MCP CONFIG GENERATOR
Generate MCP server configs for your editor
Paste an MCP server URL or a package name and get ready-to-paste config blocks for Claude Desktop, Cursor, Cline, Zed, and Windsurf. Everything runs in your browser — nothing is sent anywhere.
// About this tool
MCP Config Generator
This tool generates the MCP server configuration block you paste into an agent's settings file — Claude Desktop, Claude Code, Cursor, Cline/Roo Code, Zed, Windsurf, or a project-level mcp.json. Give it a remote server URL (https://…) or a package name (@scope/package), and it produces the correct entry for each runtime.
A URL becomes a remote entry with an url field; a package name becomes an npx entry with a pinned -y install command. The server name is derived from the URL or package and sanitized to a valid identifier.
Everything is generated locally in your browser — no input is uploaded, no account is required. For remote servers, verify the endpoint before wiring it in: pair this with the MCP Server Probe to confirm the handshake and tool list.
// When to use it
Add a remote MCP server to Claude Desktop
Paste the server's SSE or Streamable HTTP URL, copy the Claude Desktop block into claude_desktop_config.json, and restart the app.
Wire a package-based server into Cursor
Paste the npm package name (e.g. @modelcontextprotocol/server-filesystem) and copy the Cursor block into your Cursor MCP settings.
Generate a project-level mcp.json
Use the mcp.json block so every contributor to the repo gets the same MCP servers, committed to version control.
// Questions
Is this free?
Yes. Free, runs locally in your browser, no account required.
What do I paste — a URL or a package name?
Either. A URL (https://…) generates a remote server entry. A package name (@scope/package) generates an npx entry that installs and runs the server.
Which runtimes are supported?
Claude Desktop / Claude Code, Cursor, Cline / Roo Code (VS Code), Zed, Windsurf, and a project-level mcp.json. Most configs share the same shape; Zed uses an mcp key instead of mcpServers.
Does this send my URL or package anywhere?
No. The config is generated entirely in your browser. Nothing is uploaded, stored, or logged.
Should I verify a server before connecting it?
Yes. Run the MCP Server Probe on a remote endpoint first to confirm the handshake succeeds and see what tools it exposes. For package-based servers, check the package's publish history and pin a specific version instead of always installing latest.