Skip to main content

Prerequisites

1

MCP enabled for your company

The server is gated by a per-company feature flag (MCP). Ask the Qobra team to enable it for your workspace before connecting.
2

A Qobra account

You authenticate as yourself. The tools only ever return data your Qobra user is allowed to see — the same role-based permissions as the app.

Server URL

The server speaks Streamable HTTP. Qobra runs it in two regions — pick the one that matches where your Qobra workspace is hosted (the same region you log in to the app from). If you’re not sure, ask the Qobra team. There is no API key. Every client authenticates through the same OAuth 2.1 flow described in Authorize below — you only ever paste the server URL, never a secret.
Everywhere below uses the EU URL as the example. If your workspace is hosted in the US, substitute https://mcp-us.qobra.co/mcp throughout.

Add the server to your client

Open Settings → Connectors → Add custom connector, give it a name (e.g. Qobra) and paste the server URL (https://mcp.qobra.co/mcp). Leave the Advanced settings (OAuth Client ID / Secret) empty.Adding the Qobra MCP server as a custom connector in Claude
The server is protected by OAuth 2.1 + PKCE — there is no API key to copy. The flow is identical for every client (Claude, ChatGPT, Dust). On first use:
1

Discovery & registration

The client discovers the server’s OAuth metadata and registers itself automatically.
2

Consent in your browser

The client opens the Qobra consent screen in your browser. Log in to Qobra as usual (SSO / MFA included) and click Authorize.
3

Connected

The client receives a short-lived token and the Qobra tools appear in its toolbox. Tokens are scoped to your user and company, and can be revoked.