MCP Server Config Generator
Pick MCP servers, fill in the fields, and get ready-to-save config for Claude Code, Claude Desktop, and Cursor. Runs entirely in your browser, nothing you type leaves the page.
Never commit secrets to these files. Reference environment variables like
${GITHUB_TOKEN} and set the real values in your shell, so the config stays safe to check in.Generated config
Claude Code and Cursor read the same JSON shape. Claude Desktop only loads stdio servers from its config file, so a remote server is emitted as an npx mcp-remote bridge for that target. On Windows, a header value that contains spaces may need mcp-remote's environment-variable form instead. Pick a target to see its filename and path.
Save as .mcp.json
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/path/to/dir"
]
}
}
}Common questions
- Do Claude Code, Claude Desktop, and Cursor use the same config format?
- Yes. All three read a top-level mcpServers object, so the JSON is identical. Only the filename and location differ: Claude Code uses .mcp.json in your project, Claude Desktop uses claude_desktop_config.json, and Cursor uses .cursor/mcp.json.
- When do I need the type field?
- Set type to http or sse for remote servers reached over a URL. Without it a client treats the server as a local stdio command and fails to connect. Local command servers use command and args and do not need a type field.
- How do I keep tokens out of the file?
- Put a placeholder like ${GITHUB_TOKEN} as the value and export the real token in your shell. The config file then holds only the variable name, so it stays safe to commit to a repository.