Quickstart
Connect Claude to Passo and make your first call in a few minutes.
The fastest way to reach Passo from outside the dashboard is to connect an AI agent to the remote MCP server. No API key, no token handling — you authorise in the browser and the agent acts as you. This page takes you from nothing to a first result.
Connect Claude to Passo
Add the connector
In Claude Desktop or on claude.ai, open Settings → Connectors → Add custom connector and paste the Passo endpoint:
Connect an MCP client to the Passo remote server at this endpoint. The first connection opens an OAuth consent screen in your browser; approve it and the client is connected as you.
https://mcp.passo.co/v1/mcpPrefer read-only access for an agent that should never change anything? Point it at the read-only endpoint instead — the same tools with every mutating one removed:
https://mcp.passo.co/v1/mcp/readonlyPer-client setup
In Claude Desktop or claude.ai, open Settings → Connectors → Add custom connector, then paste this URL:
https://mcp.passo.co/v1/mcpFull setup for Claude Code, Cursor, VS Code and other clients is in the MCP connection guide.
Approve access
Claude opens your browser to the Passo consent screen, which names the client asking for access and the account you are signed in as. Approve it. Claude stores the tokens and refreshes them for you from now on — you will not see this screen again unless you disconnect.
If you are not signed in to Passo, you are asked to sign in first, then land back on consent.
Make your first call
Ask Claude:
Use the Passo
whoamitool to tell me which account I'm connected as.
whoami takes no arguments and returns your profile:
{
"id": "8f2c1e5a-...",
"displayName": "Ada Lovelace",
"avatarUrl": null,
"lastUsedWorkspaceSlug": "acme"
}That round trip — consent, token, one call, a result — is the whole path. Now ask for your workspaces:
List my Passo workspaces.
Claude calls list_workspaces and returns them with a total so it knows
whether more pages exist. Everything you can see in the dashboard, the agent can
now reach — and nothing you can't.
Next steps
MCP connection guide
Per-client setup and the read-only endpoint.
MCP tools
Every tool, its inputs, and example results.
Concepts
Workspaces, roles, and the vocabulary the tools use.
Authentication
The OAuth flow, token lifetime, and the RLS guarantee.
Prefer to call the REST API?
The same data is available over HTTP. The REST API is documented but published on request — talk to us if you need it — and it uses the same OAuth flow to obtain a bearer token. A call then looks like:
curl https://api.passo.co/v1/me \ -H "Authorization: Bearer $PASSO_TOKEN"{
"id": "8f2c1e5a-...",
"displayName": "Ada Lovelace",
"avatarUrl": null,
"createdAt": "2026-01-04T09:12:00.000Z",
"updatedAt": "2026-02-18T14:03:00.000Z"
}See the API reference for every endpoint and Authentication for how to obtain a token.