Agentic Data Plane

Roll Out MCP Servers to Your Claude Organization

Give every member of your Claude organization a Model Context Protocol (MCP) server from Redpanda Agentic Data Plane in Claude Desktop. An Owner adds the server once as an organization connector, each member signs in with their own Redpanda account, and Agentic Data Plane checks every tool call against that member’s permissions.

After reading this page, you will be able to:

  • Configure Agentic Data Plane to accept sign-ins from Claude and grant members access

  • Add an MCP server to your Claude organization as a custom connector

  • Verify that members can connect and call the server’s tools from Claude Desktop

This page is for administrators. To add a server to your own AI client instead, see Use an MCP Server from an AI Client.

How the rollout works

The rollout touches two products, and the same person can do both parts:

  • In Agentic Data Plane, an administrator lets Claude identify itself to the Agentic Data Plane gateway and grants members access to the MCP server.

  • In Claude, an Owner adds the server’s URL as a custom connector for the whole organization.

Claude connects to the server from Anthropic’s cloud, not from members' computers, and runs the connector through each member’s Claude account. The connector appears in Claude Desktop and on claude.ai. After a member connects, it also appears in the Claude mobile apps. The Claude Desktop configuration file holds only local servers, so you don’t edit it for this rollout.

Each member connects individually. The first time, Claude opens the Agentic Data Plane sign-in page, and the member signs in and approves access. Agentic Data Plane receives the member’s own identity with every request, so access policies and data policies apply to each person.

Claude also offers Enterprise-managed authorization, which connects members without a sign-in page. Agentic Data Plane doesn’t support it.

Prerequisites

  • A Claude Team or Enterprise plan.

  • A Claude user who can add organization connectors: an Owner, a Primary Owner, or, on Enterprise plans, a member whose custom role includes Manage access to Libraries.

  • An Agentic Data Plane user who can change inbound client settings and create access policies. See Control Who Can Do What.

  • The MCP server, created in Agentic Data Plane and listing its tools on its Inspector tab. See Create an MCP Server and Test an MCP Server’s Tools with the Inspector.

  • Members who can sign in to Agentic Data Plane with their Redpanda accounts.

  • A gateway reachable from the public internet. Claude connects from Anthropic’s IP ranges, so a server reachable only from a private network or through a VPN can’t connect.

Copy the server URL

  1. Open MCP servers in the sidebar and click the server.

  2. Click the Connection tab.

  3. Copy the Server URL.

If the server has code mode turned on, the tab also shows a Code mode URL. Decide which endpoint your members need. To roll out both, add each one as its own connector in Claude. See Code Mode.

Let Claude identify itself to the gateway

When a member signs in, Claude identifies itself to Agentic Data Plane as an OAuth client. Whoever adds the connector in Claude chooses one of three OAuth client options, and each needs matching setup in Agentic Data Plane:

Claude’s OAuth client option Setup in Agentic Data Plane

Use Claude’s published identity (Recommended)

Accept client metadata documents. Claude identifies itself with a document that Anthropic hosts at claude.ai, so you register nothing. See Accept Claude’s client metadata document.

Register automatically

Turn on self-registration with the Open admission mode, and allow the server URL. Claude registers a new client with the gateway each time a member connects, and each registration appears on the Inbound clients tab with the source DCR and a Last used time. Self-registration accepts 60 registrations an hour by default, so before a large rollout, raise Rate / hour under Guardrails. See Let clients self-register.

Use your own OAuth client

Register one client for the whole organization. Revoke all tokens on the client’s page makes every member sign in again. See Register an OAuth client for Claude.

Accept Claude’s client metadata document

If Accept client metadata documents (CIMD) is already on, and its settings already admit claude.ai and the Server URL, skip this section.

These settings apply to every client that signs in with a metadata document, not only to Claude. Before you narrow the trusted domains or the allowed resources, check which clients already sign in this way, such as Claude Code, VS Code, or Cursor, and keep every domain and URL they use. Otherwise, those clients lose access.

  1. Open Integrations setup in the sidebar and click the Inbound clients tab.

  2. Click the Self-registration card.

  3. Turn on Accept client metadata documents (CIMD).

  4. Under Trusted document domains, choose Only these domains.

  5. Click Add domain and enter claude.ai.

  6. Under Allowed resources, if the list shows Any MCP on this gateway is allowed., click Restrict….

  7. Click Add URL and paste the Server URL, without a trailing slash. The list matches URLs character for character. If you also roll out the Code mode URL, add it too.

  8. Click Save settings.

As an alternative to the domain list, Any domain admits Claude and any other client that publishes a valid metadata document.

To cover every MCP server on the gateway instead of listing URLs, click Allow any MCP on this gateway under Allowed resources, then click Save settings. This restores the setting that Allowed resources starts with when you turn on metadata documents. For the full rules, see Name the right MCP URLs.

Register an OAuth client for Claude

  1. Open Integrations setup in the sidebar and click the Inbound clients tab.

  2. Click Add external tool.

  3. Click the Claude.ai Custom Connectors card. The card fills in Claude’s redirect URIs, including https://claude.ai/api/mcp/auth_callback.

  4. Keep the suggested Name, or enter a unique one if a client already uses it. The name becomes the client ID.

  5. Under Allowed MCP Resources, click Restrict….

  6. Click Add URL and paste the Server URL. If you also roll out the Code mode URL, add it too.

  7. Under Token endpoint authentication method, choose how Claude authenticates:

    • For a client with no secret, choose None (PKCE only).

    • For a client that authenticates with a secret, keep the default, Client Secret (Basic).

  8. Click Register client.

  9. Copy the Client ID from the client’s page. If the page shows a client secret, copy it too, because it appears only once.

For every field on the form, see Connect Remote MCP Clients.

Grant members access to the server

Signing in proves who a member is. An access policy decides whether that member can open a session with the server and call its tools. Members with the Admin role need no policy. For everyone else, grant the server to the members' identity provider group:

  1. Open Access in the sidebar.

  2. On the Policies tab, click Create policy.

  3. Give the policy a name, for example claude-github-users.

  4. Set the principal to the members' group.

  5. Under Permissions, choose Template.

  6. Select the Sandboxed template.

  7. Under Applies to, choose Specific resource.

  8. Change the resource type from Agent to MCP server, then select the server.

  9. Click Create policy.

Scoped to one server, the Sandboxed template lets the group view the server, list its tools, and call them, and reaches no other resource. To grant only some tools or to add conditions, see Manage Access Policies.

Add the connector in Claude

You add the connector once for the whole organization.

This configuration refers to a third-party product. Specific UI elements may not be up to date. For current steps, see Anthropic’s Get started with custom connectors using remote MCP.
You can’t change a connector’s authentication settings after you add it. To switch options, remove the connector and add it again, and each member then reconnects.

  1. In Claude, go to Organization settings > Connectors.

  2. Click Add, hover over Custom, and select Web.

  3. Enter a name that identifies the system the server reaches, for example GitHub (Redpanda). Members see this name in their connectors list.

  4. Paste the Server URL as the remote MCP server URL.

  5. Click Continue.

  6. Review the authentication settings Claude detected.

  7. Click Continue.

  8. Under Authentication, choose Sign in now. Don’t choose No sign in, because the gateway refuses every request that lacks a signed-in member’s token.

  9. Under OAuth client, choose the option you prepared for:

    • If you accepted Claude’s client metadata document, choose Use Claude’s published identity (Recommended).

    • If you turned on self-registration, choose Register automatically.

    • If you registered a client, choose Use your own OAuth client.

  10. If you chose Use your own OAuth client, enter the client ID and, if the client has one, its secret.

  11. Click Add.

If Claude shows a single-screen dialog with a name, a URL, and Advanced settings instead, enter the name and URL, then open Advanced settings. If you registered a client, enter its client ID and secret there. Otherwise, leave both fields empty. Click Add.

Limit the rollout to some roles on Enterprise plans

On Enterprise plans, Claude roles control which members see a connector:

  1. In Claude, go to Organization settings > Roles.

  2. Open a custom role.

  3. Click the Connectors tab.

  4. Set the connector to Always allow, Needs approval, Blocked, or Custom.

Blocked hides the connector from the role, and Custom sets each tool separately. These settings apply only to members on custom roles. Members on the User, Admin, or Owner roles see every connector the organization enables. Role changes can take up to 15 minutes to reach members. For the full rules, see Anthropic’s Set up role-based permissions on Enterprise plans.

A Claude role controls who sees the connector, not what the server lets them do. Keep the access policy in Agentic Data Plane as the grant that decides who can call the server’s tools.

Connect from Claude Desktop

Each member connects once. With Claude’s published identity, the Authorize access page names Claude and notes that the name is published by claude.ai and isn’t verified by Redpanda. Tell members to expect this.

If the server uses user-delegated OAuth, the first tool call also returns a link to connect the member’s own account at the upstream system. See Connect your account to the upstream system.

Send members these steps:

  1. In Claude Desktop, go to Customize > Connectors.

  2. Find the connector by name. It carries a Custom label.

  3. Click Connect, then sign in with your Redpanda account in your browser.

  4. On the Authorize access page, check that Resource names the MCP server.

  5. Click Allow.

Verify the rollout

Before you announce the connector, ask two or three members to run these checks:

  1. In a Claude Desktop chat, click + and open Connectors.

  2. Confirm that the connector is listed and turned on.

  3. Send a prompt that needs one of the server’s tools.

  4. Confirm that the tool returns a result.

Troubleshooting

Symptom What to check

Members don’t see the connector

Ask members to look under Customize > Connectors. On Enterprise plans, check whether the member’s custom role blocks the connector, and allow up to 15 minutes after a role change.

The sign-in page shows an error instead of the Authorize access page

For Claude’s published identity, check that Accept client metadata documents (CIMD) is on, that the trusted domains admit claude.ai, and that Allowed resources lists the server URL exactly, with no trailing slash. For your own OAuth client, check that the client ID matches the client’s Client ID and that the client lists https://claude.ai/api/mcp/auth_callback.

After sign-in, the connector fails to connect, lists no tools, or denies tool calls

Check that the member has an access policy for the server. See Grant members access to the server. If the server’s Inspector tab lists no tools either, the problem is on the server.

The connector can’t connect, and no sign-in page opens

Compare the connector’s URL with the Server URL on the server’s Connection tab, and check that the server still appears on the MCP servers page. To fix the URL, remove the connector and add it again. If the URL is right, check that the gateway is reachable from the public internet.

A tool call returns a link instead of a result

Tell the member to open the link, approve access at the upstream system, and run the tool again. The server uses user-delegated OAuth, and the member hasn’t connected their upstream account yet.

Calls that worked before now fail

Ask the member to reconnect from Customize > Connectors. Either the member’s token expired and couldn’t refresh, or an administrator revoked the client’s tokens.

Next steps