MCP connection guide
Connect Claude, Claude Code, Cursor, VS Code, or any MCP client to the Passo remote server.
The Passo remote MCP server lets an AI agent read and act on your Passo data — list your workspaces, find videos awaiting review, pull a cut's version history — through the tools it exposes. This page gets you connected.
You do not create an API key or paste a token. The client discovers the server from its URL, registers itself, and sends you to an OAuth consent screen. You approve, and from then on the agent acts as you — it can see and do exactly what your Passo account can, and nothing more. See Authentication for the full flow.
Connect
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/mcpFirst connection
The first time a client connects, your browser opens the Passo consent screen showing which client is asking for access. Approve it once; the client stores the resulting tokens and refreshes them silently after that.
Read-only vs full access
Every client above can point at one of two endpoints:
- Full (
/v1/mcp) — all tools, including any that change data. - Read-only (
/v1/mcp/readonly) — the same server with every mutating tool filtered out. The tools that remain cannot alter anything in Passo.
Prefer read-only whenever the agent's job is to look — a reviewer's assistant that surfaces videos awaiting a decision, a reporting bot, anything you would not want to accidentally approve a cut. Read-only is enforced by the server, not by trusting the agent, so it is the safe default for autonomous or shared agents. Reach for the full endpoint only when the agent genuinely needs to act.
Why an endpoint, not a scope
Passo has no "read" permission you can grant at consent time — the OAuth scopes Supabase issues govern only what goes in your ID token, not what tables a tool can touch. Read-only is therefore a separate endpoint, not a checkbox on the consent screen. Choose it by URL.
Verify the connection
Once connected, ask the agent to call whoami. It returns the Passo profile the
token resolved to — confirm it is the account you expected before going further.
Then list_workspaces shows the workspaces you can reach. Both are read-only, so
they are safe to run on either endpoint. The full list of tools, their inputs and
example results is in the MCP tools reference.