MCP server config generator
Enter a local command or remote HTTP server. Pick your AI client. Get a config file with clear checks and the right project path.
Your server details stay in this browser. Usage counts contain only the client and action. Use placeholders for keys.
Choose your client
Each client expects its own file shape.
Add your servers
Use details from a server you trust. This page does not run it.
Have a JSON config? Import it
Paste a VS Code, Cursor, or Claude Code JSON config. Replace any real keys with placeholders first. Unknown settings stop the import.
Check and get your file
Project file: .mcp.json
Complete these checks
- Server 1: use a name with letters, numbers, hyphens, or underscores.
- Server 1: enter the command that starts this server.
Install in your project
- Check if
.mcp.jsonalready exists. Merge entries; do not replace your other servers. - Copy or save this file at that path.
- Replace placeholders locally, then use your client to start and trust the server.
What this check covers
The tool checks JSON import, required fields, server names, URLs, and placeholder values. Unsupported fields stop import so settings are not lost without notice.
It does not connect to a server, check its publisher, or prove that the server will start. Review commands before running them in your own client.
Supported in this version: stdio and Streamable HTTP. SSE, OAuth settings, and Codex TOML import are outside this first release. Client guides were checked on 2 October 2026.