Build a config file
Choose your client and servers. You get one file in the format that client reads, built from the same examples as each server page.
Runs entirely in your browser. Nothing you type is sent anywhere, saved, or added to the share link. By default, keys are written as environment-variable references, not values.
Client
Servers None selected
No current server matches that filter. Archived servers are not offered here.
Keys and settings
.mcp.json
This file now contains a pasted key. Don't commit it or share it; keep it out of version control.
Pick at least one server. The file appears here as you choose. Merge it into your existing config so you keep the servers you already have.
Or add them from the terminal
Where each client reads its config
Each client has its own format. Merge entries into your existing configuration, replace placeholders, then authorize any required access.
- Claude Code
- Register a server with
claude mcp add. Remote HTTP servers need--transport http..mcp.jsonholds project scope. - Claude Desktop
- Remote servers are added as custom connectors; local servers go in
claude_desktop_config.json. - Cursor
- Local processes or remote Streamable HTTP endpoints under
mcpServersin~/.cursor/mcp.json. - VS Code
- Workspace entries in
.vscode/mcp.jsonuseserverswith an explicitstdioorhttptype. - Codex
- Register with
codex mcp add, or edit~/.codex/config.toml. OAuth servers require a separate login. - Gemini CLI
mcpServersin~/.gemini/settings.json; Streamable HTTP endpoints usehttpUrl.- OpenCode
- The
mcproot in~/.config/opencode/opencode.jsonc. Local commands are arrays; credentials useenvironment. Not built here yet; each server page has its example.
How the file is built
Each server's entry comes from the same reviewed example its server page shows. Placeholders such as REPLACE_WITH_API_KEY become environment-variable references in the syntax your client expands, or the value you paste. Claude Desktop does not expand variables and adds remote servers as connectors, so the builder lists those separately. See the setup guides for where each client reads its file and how to check a server loaded.