Skip to main content
Claude connects to MCP servers through custom connectors. You add your project’s URL in Claude, choose how it signs in, and your tools show up in chat, with Interactive Tools rendering their UI in the conversation. How Claude signs in depends on your project. A Public project connects with no sign-in at all. A Private project authenticates against Metabind with OAuth: Claude opens an authorization page, you click Authorize, and Claude holds the token from then on. Either way, there’s no API key to copy or config file to edit.
No project yet? Add the public Metabind connector, https://mcp.metabind.ai/ui, the same way, with no account and no sign-in. See Try Metabind.

​
Prerequisites

  • A Claude account that can add custom connectors. Claude’s Free plan allows one custom connector. On Team and Enterprise plans, an organization owner (or, on Enterprise, a role allowed to manage connectors) adds custom connectors for the team, and members connect to them.
  • A Metabind project with at least one published Type. See Your first MCP App.
  • For a private project, a Metabind login with access to the project. The OAuth flow uses your Metabind session, so anyone who connects must be a member of the organization.

​
Get the connection URL

In Metabind Studio:
  1. Open the project.
  2. On the Server tab, switch the endpoint dropdown to Production (for the published URL) or Draft (for the working copy).
  3. Copy the URL.
The URL takes the form:
The draft URL adds /draft to the end. Use the production URL in Claude even if you’ve assigned a plugin address: Claude doesn’t render Interactive Tools served from a plugin address.
The Server tab in Metabind Studio with the endpoint dropdown open and Draft selected, showing the project's draft URL
Whether Claude asks you to sign in depends on the project’s Access setting and the URL: Change a project’s access in Project Settings → General → Access.

​
Add the connector in Claude

  1. In Claude or the Claude desktop app, open Customize → Connectors.
  2. Click Add and choose Add custom connector.
  3. Enter a Name, paste the URL from Metabind Studio into MCP server URL, and click Continue.
  4. Under Authentication, Claude detects what your URL needs and selects it for you: No sign-in for a public project’s production URL, Sign in now for a private project or the draft URL. With Sign in now, leave OAuth client on Register automatically, which Claude also detects.
  5. Click Add.
Claude's Add custom connector dialog with the Name and MCP server URL fields, open over the Customize → Connectors page
With No sign-in, the connector is ready as soon as you add it. With Sign in now, the connector opens and says you’re not connected yet. Click Connect to go to Metabind’s authorization page. Sign in if you aren’t already, review what Claude is asking to do, and click Authorize. Claude returns to the connector, now connected.
The Metabind authorization page saying the host wants to access your Metabind workspace, followed by the list of permissions it requests and the Authorize and Deny buttons

​
Verify the connection

Open the connector from Customize → Connectors. Under Tool permissions, Claude lists your project’s tools in two groups: Interactive tools (the ones that render UI) and Read-only tools. Every tool the URL serves should be there: all tools for the draft URL, published tools for production. Each group has a permission setting that controls when Claude asks before using a tool. Then start a new conversation and ask Claude to use one of your tools:
Interactive Tools render their UI in the conversation. If a tool fails, Claude shows the error inline. For deeper debugging, check Recent Executions under Analytics in Metabind Studio, which records every call from any host. Execution history is available on paid plans.

​
Draft vs. production for Claude

Treat draft and production as separate connectors in Claude:
  • Draft. Add a connector with the draft URL. Conversations see your latest unpublished work. Claude asks you to sign in with Metabind.
  • Production. Add a second connector with the production URL. This is what other people see.
On the Free plan, you can have only one custom connector at a time, so switch the URL as you go.

​
Share with other people

Anyone can add your project the same way: share the URL and they add it as a custom connector in their own Claude. For a public project, that’s all they need. For a private project, they authorize with their own Metabind login, so invite them to the organization first via Team management. To remove a connector, open it in Customize → Connectors, click ⋯, and choose Remove.

​
Troubleshooting

Connect to ChatGPT

Same project, different host.

Custom MCP hosts

Connect any MCP-compatible client.

Draft and production

Why two endpoints exist and when to use each.

Public and private projects

What public access allows.