MCP connector

Kabaido runs a Model Context Protocol server at /api/mcp using streamable HTTP. It gives AI assistants scoped, read-mostly access to your organisation plus the ability to raise requests. Available on plans that include API access.

Connect from Claude

1. In Claude open Settings, then Connectors, then Add custom connector.
2. Paste https://kabaido.ai/api/mcp and continue.
3. Claude sends you to Kabaido to sign in. Pick the organisation and the scopes to grant, then Allow access.

The connection uses OAuth with PKCE; no key is pasted anywhere. You can revoke it at any time from Settings, then Integrations, on the Claude or Any MCP client entry.

Connect from Claude Code

claude mcp add --transport http kabaido https://kabaido.ai/api/mcp \
 --header "Authorization: Bearer kbd_your_key_here"

Connect from Cursor and other clients

{
 "mcpServers": {
 "kabaido": {
 "url": "https://kabaido.ai/api/mcp",
 "headers": { "Authorization": "Bearer kbd_your_key_here" }
 }
 }
}

Tools

A tool call outside the connection's scopes returns a clear error rather than data. Scopes are fixed when the connection is approved; reconnect to change them.

Usage through the connector

Reading data over MCP costs nothing, like browsing the app. Actions that create work differ by credential. Through an API key, create_request is free, the same as the REST API. Through an OAuth connector such as the Claude connector, create_request draws on your usage at twice the standard line weight, because the assistant's reasoning runs on your own AI account rather than the Kabaido AEI; the connector deposits finished work, so the platform meters it at 2x in place of the per-line AEI charges it bypasses. A connection reaching an exhausted allowance receives a clear error instead of silently failing.

What this is actually for

The useful shape is a question you would otherwise have answered by opening four screens. "Which quotes over five thousand pounds are still open with customers who have not ordered since March?" is not a report anybody built, and it is the kind of question an assistant with read access to quotes, orders and customers can answer in one go.

The other shape is intake: an assistant that has been handed an enquiry can raise it as a request your team sees, without anyone copying text between windows.

The scope ceiling

A connection can never grant more than the person approving it already has. A sales member approving a connector cannot hand it engineer powers, because the scopes are capped by their own role at the moment of approval. That is what makes it safe to let people connect their own assistants without an admin auditing every one.