ZuploZuplo
LoginStart for Free
  • Documentation
  • API Reference
Getting Started
Concepts
API Management
AI Gateway
MCP Gateway
    Overview
    Getting Started
      How it works
      Connect MCP clients
        OverviewClaude DesktopClaude CodeChatGPTCursorVS CodeOther clientsTest clients
      Authentication
      Cross App Access
      Configuration
      Policies
      Observability
      ReferenceServer RegistryTroubleshooting
    MCP Server
    Developer Portal
    Development
    Deploying & Source Control
    Analytics
    Observability
    Networking & Infrastructure
    Account Management
    Programming API
    Build with AI
    Zuplo CLI
    Migration Guides
    Platform LimitsVersion Support PolicySecuritySupportTrust & ComplianceChangelog
    powered by Zuplo
    Connect MCP clients

    Connect Claude Desktop and Claude.ai

    Claude Desktop and Claude.ai connect to remote MCP servers through Custom Connectors. Adding a Zuplo MCP route takes two steps: paste the route URL into Claude's connector settings, then complete the browser-based OAuth flow.

    Prerequisites

    • A Zuplo project with the MCP Gateway plugin configured and at least one MCP route. See the quickstart if you haven't set one up yet.
    • Claude Desktop installed, or access to Claude.ai in your browser.
    • A Claude plan that supports custom connectors. Per Anthropic's documentation, custom connectors are available on Free, Pro, Max, Team, and Enterprise plans. Free plans are limited to one custom connector. Team and Enterprise plans require an organization owner to add the connector first before individual members can authenticate.

    Get the route URL

    Each MCP route in config/routes.oas.json is reachable at https://{deploymentUrl}/{routePath} once deployed. The {routePath} is the path you set on the route — for example /mcp/linear-v1.

    Native remote connectors connect from Anthropic's servers, so the gateway URL must be reachable from those servers. For a gateway running locally with zuplo dev, use the manual configuration with http://127.0.0.1:9000/{routePath}.

    Add the connector in Claude

    Both Claude Desktop and Claude.ai support custom connectors. The flow is nearly identical in each.

    1. Open connector settings. In Claude Desktop or Claude.ai, open Customize → Connectors.

    2. Add a custom connector.

      Click +, then Add custom connector.

    3. Enter the gateway URL.

      Paste the route URL (for example https://{deploymentUrl}/mcp/linear-v1). Optionally name the connector (the name is what Claude shows you in the connector list and in tool results) and click Add.

    4. Sign in to the gateway.

      Claude opens the gateway's OAuth flow in a browser. Sign in with the identity provider you configured for the gateway — see the provider catalog for the full list of supported IdPs.

    5. Complete the upstream connection.

      The gateway shows a consent page with the upstream MCP server the route proxies to. Click Connect next to the upstream and complete its OAuth flow. Once it's connected, click Authorize to finish.

    6. Verify the connector is active.

      Back in Claude, the new connector appears in your Connectors list. Open a chat and click the attachment icon to confirm tools, prompts, and resources from the gateway are available.

    You can adjust which tools Claude is allowed to use per connector. Open the connector in Customize → Connectors and toggle individual tools on or off.

    What Claude Desktop supports

    Claude Desktop registers itself with the gateway through Dynamic Client Registration (DCR).

    Claude Desktop supports the following MCP capabilities from the gateway:

    • Tools — invoke gateway-exposed tools by name.
    • Prompts — surface prompts as commands in the chat interface.
    • Resources — attach resources to messages from the attachment menu.
    • Roots — declare filesystem boundaries to the server.
    • MCP Apps — render interactive HTML widgets inline in the conversation.

    Claude.ai (the web version) supports the same set, plus Client ID Metadata Documents (CIMD) in addition to DCR.

    Use a manual config file (advanced)

    If you need to script the install or share the configuration with a team, Claude Desktop also reads claude_desktop_config.json. This approach uses mcp-remote as a stdio bridge to the gateway. Use it for a gateway running on your computer or when you need file-based configuration. This approach requires Node.js and npx.

    1. In Claude Desktop, open Settings → Developer → Edit Config. This opens claude_desktop_config.json in your editor.

    2. Add or merge in the following entry, replacing Zuplo MCP with the name you want to show, and the URL with your route URL. For local development, use http://127.0.0.1:9000/{routePath} instead of the HTTPS URL and append "--allow-http" to the args array:

      Code
      { "mcpServers": { "Zuplo MCP": { "command": "npx", "args": ["-y", "mcp-remote", "https://{deploymentUrl}/{routePath}"] } } }
    3. Save the file and restart Claude Desktop.

    4. The first time Claude Desktop starts the bridge, it opens a browser window to complete the OAuth flow against the gateway. Sign in and approve the consent page as you would for a native connector.

    5. Verify the server appears in Claude Desktop. Tools are available behind the attachment icon.

    Use native custom connectors for a deployed gateway. They do not require Node.js. Use the mcp-remote bridge for a local gateway or file-based configuration.

    Troubleshooting

    • Browser does not open during OAuth. Verify the gateway's deployment URL is reachable from your machine and your firewall or proxy allows outbound HTTPS to the gateway origin.
    • Consent page shows "Connect" for every upstream every time. This means the gateway never received the user's signed-in identity. Confirm that your IdP is configured correctly and that browser cookies are enabled for the gateway origin.
    • Tools do not appear after a successful authorization. Open the connector in Customize → Connectors and check that each tool is enabled. Disabled tools are hidden from the attachment menu.

    Related

    • Connect MCP clients overview
    • To route Claude Desktop's model requests through Zuplo instead, see the Claude Desktop AI Gateway integration
    • Anthropic's official guide: Connect to remote MCP servers
    • Anthropic's setup article: Get started with custom connectors using remote MCP
    • Authentication overview
    Edit this page
    Last modified on September 23, 2026
    OverviewClaude Code
    On this page
    • Prerequisites
    • Get the route URL
    • Add the connector in Claude
      • Open connector settings. In Claude Desktop or Claude.ai, open Customize → Connectors.
      • Add a custom connector.
      • Enter the gateway URL.
      • Sign in to the gateway.
      • Complete the upstream connection.
      • Verify the connector is active.
    • What Claude Desktop supports
    • Use a manual config file (advanced)
    • Troubleshooting
    • Related
    JSON