What this tool does
MCP Config Generator drafts and validates Model Context Protocol server configuration snippets for stdio and HTTP-style servers.
← All Tools
🔌 MCP Config Generator
Generate MCP server config JSON for stdio and HTTP transports, validate the shape, catch risky env-var mistakes, and copy reproducible config examples. This is local config generation only: it does not connect to MCP servers, install packages, or call external services.
Claude Code user MCP configuration · Client documentation
Validation checks
- Portable server names and the selected client’s canonical
mcpServers,servers, or endpoint-only shape. - stdio command/args vs HTTP URL/header placement.
- Environment variable name syntax and empty values.
- Secret-like values that should be placeholders such as
${UTILITO_API_TOKEN}, not live credentials.
Local-only workflow
This tool drafts JSON for your MCP client and validates common shape issues in the browser. It does not connect to MCP servers, test credentials, start commands, or verify a remote endpoint.
Use the generated config as a starting point, then compare transport and client-specific fields against your MCP server and client documentation before sharing it with an agent team.
Why it is useful
It helps agent builders draft local or remote MCP server entries for compatible clients with fewer syntax mistakes, clearer transport choices, and safer environment-variable handling.
How it works
The browser combines server name, client target, transport, command or URL, arguments, and env/header fields into config JSON, then validates the generated shape without connecting to any MCP server.
Best input
Use exact command paths, package names, arguments, and environment variable names from the MCP server documentation and your MCP client documentation.
Integration tip
Keep secret values out of generated examples; reference environment variable names or placeholders instead, then pair this config with schema and tool-calling validators before wiring an agent.
Privacy note
Config generation and validation happen locally in your browser.
Important limitation
MCP clients and servers can differ in supported config shape, transport, and security expectations. Verify with your MCP server and client documentation before relying on a generated config.
Quick answers
Does this install MCP servers?
No. It only drafts and validates config snippets.
Does this connect to MCP servers?
No. It does not connect to MCP servers, run commands, test credentials, or call remote endpoints.
Should I include API keys?
No. Use environment variable names or placeholders, not secret values.
Common Use Cases
Create a local stdio MCP config
Generate a config for an npm, Python, or local binary MCP server using one argument per line.
Draft an HTTP MCP endpoint config
Switch to HTTP mode to produce a URL-based server entry with optional header placeholders.
Catch unsafe secret handling
Scan env/header lines for malformed names and secret-like values before sharing a config with teammates or agents.
Agent MCP and tool schema workflow
Draft MCP client config, generate tool schemas, convert JSON Schema into provider tool definitions, and validate tool-call payloads before wiring an agent.