HCODX/MCP Config Generator
Model Context Protocol · Claude Desktop · Cursor · Zed · Continue

MCP Server Config Generator: build valid JSON in seconds

Generate Model Context Protocol server configurations for Claude Desktop, Cursor, Zed, and Continue. Pick a transport (stdio/SSE/HTTP), fill the form, get production-ready JSON. Includes presets for Filesystem, GitHub, Postgres, and Linear MCP servers.

Quick presets
Server definition
Generated config

      
Client
Claude Desktop
Transport
stdio
Env vars
0
Status
Valid
Use cases

Why use a generator?

MCP configs are JSON — small typos break silently. A form-driven generator catches those bugs before they cost you debugging time.

Add MCP servers in seconds

Skip hand-editing JSON — fill the form, get a valid config, paste it into your client.

Multi-client output

Switch the target dropdown to get Claude Desktop, Cursor, Zed, or Continue formats — all from the same form.

One-click presets

Filesystem, GitHub, Postgres, and Linear servers preconfigured — tweak and ship.

Download or copy

Copy to clipboard or download as a .json file ready to drop into your config directory.

Step by step

How to add an MCP server

1

Pick a preset or fill the form

Use a quick preset for common servers (filesystem, GitHub, Postgres, Linear), or define your own command, args, and env vars.

2

Choose your client

Claude Desktop, Cursor, Zed, Continue — each gets the right wrapper format automatically.

3

Paste into your config

Copy the JSON, paste into your client's config file (see FAQ for paths), restart the client. Done.

FAQ

Frequently asked questions

MCP is an open standard from Anthropic that lets AI assistants connect to external data sources and tools. An MCP server exposes capabilities (files, databases, APIs) to an MCP client (Claude Desktop, Cursor, Zed, Continue). The client speaks a JSON-RPC dialect over stdio, SSE, or HTTP.

It depends on the client. Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%/Claude/claude_desktop_config.json on Windows. Cursor: settings.json under mcp.servers. Zed: settings.json under context_servers. Each preset above includes the exact path in the output comment.

stdio is the most common — the client spawns the server as a subprocess and talks over stdin/stdout. SSE (server-sent events) keeps a persistent HTTP stream open for long-lived servers. HTTP is plain request/response for stateless tools. stdio is best for local tools; SSE/HTTP are best for remote or cloud-hosted MCP servers.

100% local — this generator never sends your config anywhere. All form values, env vars, and the resulting JSON stay in your browser. You can use it offline once the page is loaded. Be careful pasting real API keys into the env section if you take a screenshot.

About

About the Model Context Protocol

The Model Context Protocol is an open standard introduced by Anthropic in late 2024 to give AI assistants a uniform way to talk to tools, data sources, and external systems. By 2026 every major AI client supports it natively — Claude Desktop, Cursor, Zed, Continue, and a growing ecosystem of third-party clients.

Anatomy of an MCP server config

  • name — the key the client uses to refer to this server. Must be unique within the config.
  • command — for stdio transport, the binary the client should spawn. Common values: npx, uvx, python, node, or a direct path.
  • args — array of arguments passed to the command. Order matters.
  • env — object of environment variables (API keys, paths, configuration) injected into the spawned process.
  • url — for SSE/HTTP transports, the endpoint the client connects to.

Common server packages

  • @modelcontextprotocol/server-filesystem — expose a directory to the AI. npx -y for instant install.
  • @modelcontextprotocol/server-github — read repos, issues, PRs. Needs GITHUB_PERSONAL_ACCESS_TOKEN.
  • @modelcontextprotocol/server-postgres — SQL queries against a Postgres database. Connection string as arg.
  • linear-mcp — Linear issue tracker via SSE. Hosted endpoint, OAuth-based.

Client formats

Claude Desktop wraps servers in {"mcpServers": {"name": {...}}}. Cursor uses {"mcp": {"servers": {...}}}. Zed uses {"context_servers": {...}}. The differences are cosmetic but matter — paste the wrong shape and the client silently ignores it. This generator handles the wrapping for you.

Related

Related tools