MCP, set up
for your client.
A remote MCP server is one URL. The setup is different in every client. Pick the software you use for the exact command, config path, and approval step.
The most-used MCP clients
These clients support remote MCP servers directly. Each guide shows the project and global config paths, the setup shape, and the approval behavior.
OpenCode
People who want one native MCP setup across the terminal and editor.
opencode.jsoncClaude Code
Teams that want MCP servers committed with the project and reviewed.
.mcp.jsonClaude Desktop
Chat workflows where you want the same remote tools in every conversation.
Settings > ConnectorsCodex
Terminal-first work with a clear approval boundary.
.codex/config.tomlCursor
Editor-led work where the MCP server belongs with the code.
.cursor/mcp.jsonVS Code
Copilot users who want MCP tools beside their editor.
.mcp.jsonGitHub Copilot CLI
Terminal work in GitHub-centric repositories.
.mcp.jsonGemini CLI
Terminal workflows in the Google ecosystem.
.gemini/settings.jsonAntigravity
Antigravity users who switch between the app, IDE, and CLI.
~/.gemini/config/mcp_config.jsonChoose your client
Every guide is grounded in the client's current documentation. Native setup steps are shown where a client has its own CLI; the rest use the client's documented config shape. If a client is global-only, the guide says so instead of inventing a project path.
Factory Droid
Project MCP for Factory's coding agent.
.factory/mcp.jsonJunie
MCP inside JetBrains and the Junie CLI.
.junie/mcp/mcp.jsonKiro CLI
The same MCP config in Kiro's IDE and CLI.
.kiro/settings/mcp.jsonWindsurf
Project, local, and user MCP configs in the Devin Local docs.
.devin/mcp_config.jsonZed
MCP servers in Zed's agent panel.
.zed/settings.jsonInstall a server from its page
Every server page has a client selector. It shows the config shape for the real endpoint, server name, and transport. Use this shape when you already have a URL.
opencode mcp add example --url https://mcp.example.com/mcp{
"mcpServers": {
"example": {
"url": "https://mcp.example.com/mcp"
}
}
}- 1Find the server in the MCP directory.
- 2Choose your client in the sidebar and copy the setup details.
- 3Restart the client, authorize if asked, and ask for a task.
One protocol, different client plumbing
MCP is the interface between a client and a server. Each client still has its own config file, scope rules, and approval model.
The server advertises tools
A remote MCP server exposes tools, resources, and prompts. The client discovers them when it connects; you do not write tool definitions by hand.
The client holds the config
The URL lives in the client's own config file. Some clients support project and global scopes; others are global-only or read a single shared file.
The provider controls access
OAuth, API keys, rate limits, and tool permissions belong to the provider. The setup guide links to the provider's docs rather than guessing.