Connect Your AI Assistant

Prerequisites

• An Orbb account (the same one you use to sign in to app.orbb.com)
• MCP access enabled for your organization — it is off by default; contact your Orbb customer team to enable it
• An AI assistant that supports remote MCP servers over Streamable HTTP with OAuth

The connection details are the same in every client:

Name	Orbb
Server URL	https://mcp.orbb.com/mcp

Claude (web and desktop)

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Enter the name Orbb and the server URL https://mcp.orbb.com/mcp, then confirm.
4. A browser window opens asking you to sign in to Orbb. Sign in with your Orbb account and approve the requested access.
5. That's it — in a conversation, Claude can now use Orbb tools. Try asking: "Who at my company has the strongest path into Acme Corp?"

Claude Code

Run:

claude mcp add --transport http orbb https://mcp.orbb.com/mcp

Then run /mcp inside Claude Code to complete the sign-in flow in your browser.

Other MCP clients

Any MCP client that supports remote servers over Streamable HTTP with OAuth 2.1 can connect. Point it at https://mcp.orbb.com/mcp; the server advertises its authorization details through standard OAuth discovery metadata, and clients register automatically — no client ID, secret, or API key is required. Complete the sign-in prompt with your Orbb account when the client opens it.

Signing in and approving access

During setup you are redirected to Orbb's sign-in page. The requested permissions are limited to your profile, email, and Orbb organization membership — this is how the server knows who you are and which organization's data you may access. Your assistant never sees your Orbb password; it receives only a scoped access token.

Disconnecting

• From your assistant: remove the Orbb connector in the client's settings (e.g. Settings → Connectors in Claude, or claude mcp remove orbb in Claude Code). This discards the client's access.
• Organization-wide: your Orbb customer team can disable MCP access for the entire organization at any time, which immediately blocks every connected client.
• Per user: deactivating a user's Orbb account revokes their MCP access along with everything else.

Troubleshooting

• "MCP access is not enabled for this organization" — your organization hasn't opted in yet; contact your Orbb customer team.
• Sign-in loop or authorization errors — remove the connector and add it again to restart the OAuth flow with fresh credentials.