MCP Server Config Generator
Fill in your server's command, arguments, and environment variables. Get a generic JSON config, Claude Desktop format, Cursor/Windsurf reference, .env example, and a README snippet โ instantly, in your browser.
Server Configuration
Used as the key in client config files. Use kebab-case.
The executable to run. Should be on your PATH or an absolute path.
Arguments
Environment Variables0 defined
Mark sensitive variables as Secret โ they will show as placeholders in output and the .env example will remind you not to commit them.
Notes (optional)
// Fill in server name and command to generate configโฆ
Verify with your MCP client. Config file location and exact JSON format differ between clients (Claude Desktop, Cursor, Windsurf, VS Code extensions, etc.). The snippets here are reference examples โ always check your client's official documentation before using them.
MCP Server Config Guide
Common config fields
| Field | Required |
|---|---|
| name | Yes |
| command | Yes |
| args | No |
| env | No |
| cwd | No |
| transport | No |
Common mistakes
Command not on PATH
If "node" or "python" aren't found, the client silently fails to start the server. Use absolute paths (/usr/local/bin/node) or ensure the binary is on your PATH.
Hardcoded secrets in config
Pasting API keys directly into the JSON config is dangerous if the file is ever committed to git. Always use environment variables for secrets.
Assuming one config format
Claude Desktop, Cursor, Windsurf, and VS Code extensions each have their own config file and may use slightly different schemas. Never copy a config from one client and assume it works in another.
Wrong working directory
If your server uses relative paths to load config files or modules, the process must be started from the right directory. Set cwd explicitly if needed.
Forgetting to rebuild
For compiled servers (TypeScript, Go, Rust), the config runs the compiled output โ not the source. Remember to rebuild after code changes, or use a dev watcher.
Server exits immediately
A server that crashes on startup is often missing required environment variables or has a wrong entrypoint path. Run the command manually in your terminal first to see the error.
Config format varies by client
The snippets this tool generates are reference examples. MCP clients each define their own config file location and JSON schema. Always verify the exact format in your client's documentation before using a config snippet. Do not blindly copy a snippet from one client and use it in another.
Privacy: This tool runs entirely in your browser. Your server names, commands, and environment variable values are not uploaded or stored anywhere.
Frequently Asked Questions
What is an MCP server config?
Does every MCP client use the same config format?
What is the "command" field?
What is the difference between stdio, HTTP, and SSE transports?
Should I put API keys directly in the config?
What is the working directory (cwd) field for?
What does the TypeScript / README snippet output contain?
Related Tools
MCP Tool Definition Generator
Generate MCP tool definitions from a form โ name, description, typed input fields, and required arrays.
MCP Tool Schema Validator
Validate MCP tool definitions โ names, descriptions, inputSchema, required fields, and common mistakes.
OpenAPI to MCP Generator
Convert OpenAPI JSON or YAML specs into MCP tool definitions, input schemas, and TypeScript skeletons.