Connecting to MCP clients
Connect an MCP (Model Context Protocol) Surface to MCP-compatible clients through its HTTP endpoint. Choose OAuth, an API key, or no authentication for the connection.
Use this URL pattern:
Replace YOUR_PRODUCT_ID and YOUR_SURFACE_ID with the IDs from your Product and Surface. Find the exact URL in the Ship tab of your MCP Surface.
Choose an authentication mode
Select an authentication mode in the Ship tab. Use this table to choose the mode for your client:
In OAuth mode, the client completes the OAuth flow when you connect the URL. In API Key mode, create an API key in the Keys tab and include it in the client configuration. Runtype prefixes MCP Surface keys with mcp_.
Claude Desktop
Use OAuth or Public mode to connect a remote MCP Surface to Claude Desktop. Claude Desktop adds remote MCP servers through Settings > Connectors. It does not load remote servers from claude_desktop_config.json.
OAuth
API key
Connect an OAuth-enabled MCP Surface in Claude Desktop with these steps:
- Open Settings > Connectors.
- Add a custom MCP connector.
- Paste the MCP server URL from the Ship tab.
- Complete the authorization flow in the browser.
Claude Code
Add the MCP Surface to Claude Code with one of these commands:
OAuth
API key
Run this command in your terminal:
Replace YOUR_PRODUCT_ID and YOUR_SURFACE_ID with the IDs from your Product and Surface. Claude Code prompts you to authorize in the browser.
Run claude mcp list to confirm that the server connects. Run claude mcp remove your-product to disconnect it.
Cursor
Connect the MCP Surface to Cursor with one of these methods:
OAuth
API key
Use these steps to add an OAuth-enabled MCP Surface:
- Open Customize > MCPs.
- Click Add New MCP Server.
- Paste the MCP server URL from the Ship tab.
- Complete the authorization flow in the browser.
VS Code (GitHub Copilot)
Add the MCP Surface to .vscode/mcp.json in your workspace:
OAuth
API key
Add this configuration to .vscode/mcp.json:
Replace YOUR_PRODUCT_ID and YOUR_SURFACE_ID with the IDs from your Product and Surface. VS Code opens a browser for OAuth when the server first connects.
Save the file. If VS Code asks you to trust the server, approve it. Open the Chat view and use Configure Tools to confirm that the tools are available.
VS Code (Cline)
Add the MCP Surface to Cline with these steps:
- Open the Cline panel.
- Open Settings.
- Open MCP Servers and click Edit MCP Settings.
- Add the MCP server URL.
- If you use API key authentication, add the
Authorization: Bearer YOUR_API_KEYheader. ReplaceYOUR_API_KEYwith your API key. - Save the configuration and reopen the Cline panel.
Windsurf
Add the MCP Surface to ~/.codeium/windsurf/mcp_config.json:
Replace YOUR_PRODUCT_ID, YOUR_SURFACE_ID, and YOUR_API_KEY with your values. If your Surface uses OAuth or Public mode, omit the headers block.
JetBrains IDEs
Use these steps in IntelliJ IDEA, WebStorm, PyCharm, or another JetBrains IDE with AI Assistant enabled:
- Open Settings > Tools > AI Assistant > Model Context Protocol (MCP).
- Click + to add a server.
- Select the HTTP connection type.
- Enter the MCP server URL.
- If you use API key authentication, add the
Authorization: Bearer YOUR_API_KEYheader. ReplaceYOUR_API_KEYwith your API key. - Click OK.
- Click Apply.
Any other MCP client
If your client accepts an mcpServers JSON object, adapt this template:
Replace YOUR_PRODUCT_ID, YOUR_SURFACE_ID, and YOUR_API_KEY with your values. For OAuth-enabled or Public Surfaces, omit the headers block. A client that supports MCP OAuth discovery completes authentication automatically.
Use this URL to inspect the MCP manifest:
Replace YOUR_PRODUCT_ID and YOUR_SURFACE_ID with the IDs from your Product and Surface.
Verify your connection
After you connect, use these checks to confirm that the client lists your Capabilities as tools:
- Claude Desktop: Open a chat and check the tools list.
- Claude Code: Run
claude mcp listand confirm the server status. - Cursor: Open the MCP tools list in the chat panel.
- VS Code (Copilot): Open Configure Tools in Chat and confirm the tools.
Ask the client to call one of your tools by name. If no tools appear, confirm that the Surface status is Active and that at least one Capability is enabled in the Endpoints tab.
Troubleshooting
Tools do not appear
If tools do not appear, run these checks:
- Confirm that the Surface status is Active.
- Confirm that at least one Capability is enabled in the Endpoints tab.
- Restart or reload the client after you add the configuration.
- If you use API key authentication, confirm that the key starts with
mcp_and remains active.
Authentication fails
If authentication fails, run these checks:
- Complete the browser authorization flow for OAuth.
- Check the API key and header for typos.
- Confirm that the API key belongs to this Surface.
- For more information, read MCP authentication.
Connection times out
If the connection times out, run these checks:
- Confirm that the URL matches the URL in the Ship tab.
- If a corporate network blocks outbound connections, try another network.
Next steps
Continue with one of these guides:
- Setting up an MCP Surface: create and configure your Surface
- MCP authentication: manage keys and authentication
- Scoping API keys to capabilities: restrict access to selected Capabilities
- Adding capabilities to a Product: expose more tools