Skip to main content
Every client connects to the same endpoint:
What differs is where the config lives and what the file looks like. Pick your client.

​
Clients with browser authorization

These handle OAuth themselves. You add the URL, they open a browser on first connect, and they store the credential outside your config file. No secret in mcp.json.

Claude Code

One command in your terminal.

Claude Desktop

Settings, Connectors, paste the URL.

Cursor

~/.cursor/mcp.json

Windsurf

~/.codeium/windsurf/mcp_config.json

VS Code

.vscode/mcp.json, version 1.102 or newer.

ChatGPT

Business and Enterprise workspaces.

Grok

Connectors on grok.com.

Codex CLI

codex mcp add, then log in.

Gemini CLI

~/.gemini/settings.json

​
Anything else

If your client speaks MCP over Streamable HTTP, it will work. See compatible MCP clients for the shape most clients expect and what to do when yours needs a key instead of OAuth.

​
After you connect

Start a fresh session so the client re-reads its server list, then ask a question that needs live data. Quickstart has a couple that make it obvious whether the connection is working.