MCP Server Config Generator

What this MCP server config generator does

The Model Context Protocol (MCP) lets an AI client connect to external tools and data through a small JSON or TOML configuration block. Each client reads that block slightly differently, which is where mistakes happen. This generator turns one server definition into a correct, paste-ready config for every major client at once.

Two kinds of MCP server

• Local (stdio): the client launches the server as a child process and talks to it over standard input and output. You supply a command, its arguments, and any environment variables such as API keys.
• Remote (Streamable HTTP): the server runs as a network service. You supply a URL and optional headers, such as an Authorization bearer token.

The generator asks which transport you want and shows only the fields that apply.

Clients it covers

• Claude Code and Claude Desktop use the mcpServers object in .mcp.json. Remote servers add a type of http.
• VS Code uses a servers key with an explicit type of stdio or http.
• Cursor reads the same mcpServers shape from the Cursor config file.
• Codex CLI uses TOML, with a table per server and inline http headers for remote servers.

How to use it

1. Enter a server name, which becomes the key in the config.
2. Choose stdio or remote.
3. For stdio, add the command, each argument, and any environment variables. For remote, add the URL and headers.
4. Copy the tab for your client.

A note on secrets

Never paste a real API key into a config you commit to source control. Use an environment variable reference instead, and keep the secret in your shell or a secrets manager.

Related

Learn the concepts in our guides on what an MCP server is and the Model Context Protocol, and check any pasted config with the MCP Config Validator.