Passo Developer Docs
The public REST API and remote MCP server for Passo workspaces.
Passo gives brands one place to run creator video: brief the work, review cuts, approve deliveries. This site documents the two ways to reach that data from outside the dashboard — a remote MCP server for AI agents and a REST API for code.
Both authenticate the user, not an app: an agent or script sees exactly what the person who authorised it can see, and nothing more. That is not a policy we enforce by hand — it is the same row-level security the dashboard runs on. See Authentication for why.
Start here
Quickstart
Connect Claude to Passo and make your first call in a few minutes.
MCP connection guide
Endpoint, OAuth, and per-client setup for Claude, Claude Code, Cursor, VS Code, and generic clients.
Authentication
The OAuth 2.1 flow end to end — consent, tokens, refresh, and the RLS guarantee.
Concepts
Workspaces, roles, and the vocabulary — including why a brand is a workspace.
Reference
MCP tools
Every tool the remote MCP server exposes, generated from the committed inventory.
API reference
Every REST endpoint, generated from the OpenAPI spec.
The REST API is documented here but published on request; the MCP server is public today. Conventions covers pagination, errors, and versioning for both, and the Changelog records every change to the contract.