MCP Config Generator

Generated an MCP client config block and a server command snippet.

How it works

• Read the server name, transport and the command/args/env or url you supplied.
• Emit a `mcpServers` JSON block for your MCP client.
• Emit a server command snippet for the stdio transport.

• Secret-like environment values are written as placeholders so a real key is never baked into a copy-pasteable file.
• This tool only formats text; it never launches a process or opens a connection.

Methodology

1. Build a `mcpServers` object keyed by the server name: a stdio entry carries `command`, `args` and `env`, and an SSE entry carries `url`.
2. Render JSON with stable two-space indentation so the output is deterministic.
3. Replace the value of secret-like environment keys with an upper-cased placeholder and emit a matching server command snippet.

Usage

1. Enter a server name and choose the stdio or SSE transport.
2. For stdio, provide a command, one argument per line, and optional `KEY=value` environment lines.
3. For SSE, provide the server URL, then copy the config block into your MCP client.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

A local stdio server

{
  "name": "filesystem",
  "transport": "stdio",
  "command": "npx",
  "args": "-y\n@modelcontextprotocol/server-filesystem\n/tmp",
  "env": "",
  "url": ""
}

A remote SSE server

{
  "name": "remote",
  "transport": "sse",
  "command": "",
  "args": "",
  "env": "",
  "url": "https://mcp.example.com/sse"
}

Limitations

How MCP clients are configured

MCP hosts such as Claude Desktop read a configuration that maps a server name to a transport: stdio servers run a local command with arguments and environment, while remote servers are reached over a URL. This generator writes that block for the values you provide.