Skip to main content
Every client takes the same thing: a server URL. Most then open a browser for you to sign in to Orbb, and calls arrive as you.
In claude.ai or the desktop app, open Settings → Connectors → Add custom connector, paste the server URL, and choose Connect. A browser window opens the Orbb sign-in.An organization owner can add the connector once for the whole team; each person then signs in as themselves.

Signing in

OAuth

Both servers are OAuth 2.1 resource servers. An unauthenticated call is answered 401 with a WWW-Authenticate header pointing at the server’s protected-resource metadata, which names the authorization server; clients register themselves dynamically. You only paste the URL.The workspace server also needs your organization to have MCP access turned on. Without it, every tool answers “MCP access is not enabled for this organization.” — ask your Orbb admin.
Send Authorization: Bearer orbb_sk_… — the same key the API takes, created under API keys. Research runs are charged to that key’s account.The workspace server does not take keys.
A plan belongs to the credential that made it. Orbb Research keeps one conversation per API key, or per signed-in person, and a plan can only be started from that conversation. An agent that plans with one key and starts with another gets plan not found.

Check it works

Ask your assistant: “Using Orbb, what can you answer?” It should call orbbai_capabilities and describe what Orbb covers and what it needs your own data for.