FAQ

The Passo MCP server uses bearer token authentication. Generate an API key in your Passo dashboard (Workspace Settings → API Keys). The key format is passo_ followed by 64 hex characters. Pass it in the Authorization header as "Bearer YOUR_KEY". Each key is scoped to one workspace.

Streamable HTTP (stateless). GET, POST, and DELETE are all handled on the same endpoint: https://pro.passo.co/api/mcp. SSE is not supported.

You'll get a 401 response with {"error":"invalid_token","error_description":"No authorization provided"}. Double-check that you're sending the key in the Authorization header as a Bearer token.

Yes. You can create multiple keys per workspace. Each key has the same permissions — they're all scoped to the workspace. Revoke unused keys from Workspace Settings → API Keys.

Yes, but they're generous for normal usage. If you hit a rate limit, you'll get a 429 response with a Retry-After header. Typical agent workflows stay well within limits.

API keys are workspace-scoped. A key can access all tools available to the workspace. There are no per-tool or per-resource scopes at this time.

Go to Workspace Settings → API Keys in the Passo dashboard and delete the key. It takes effect immediately.

OAuth 2.1 support is planned. When it ships, you'll be able to connect without managing API keys — just add the URL and authorize through your browser.

Any MCP client that supports streamable HTTP and custom headers. This includes Claude Code, Claude Desktop, Claude.ai, and third-party MCP clients.

No. create_sourcing_campaign creates a draft with sourcing OFF. No creators are contacted and no budget is spent until you explicitly call start_sourcing_agent.

No. create_automation_flow creates an inactive draft. Nothing runs until you explicitly call publish_automation_flow or publish from the dashboard.

Several MCPs give agents creator data — discovery, analytics, fraud checks. Passo runs the program. Data MCPs end at discovery: your agent finds creators but has no campaign state, so it still re-sources the same people, and it still can't send outreach, generate contracts, review content, or pay anyone. Passo is the system of record plus the execution layer — and if you already source creators elsewhere, you can import them and Passo's never-source-twice guarantee covers them too. See our full comparison: /blog/posts/creator-data-mcp-vs-creator-operations-mcp

No. Passo works with any creator via email. There's no marketplace opt-in or network requirement.

Passo is the AI operating system for influencer teams. It's an AI co-worker that runs your influencer program end-to-end — from sourcing creators to reviewing content to handling payments — without requiring creators to join a marketplace.

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude connect to external tools and data sources. The Passo MCP server lets your AI agent source creators, manage campaigns, and automate outreach directly from a conversation.

Book a 30-minute demo with the founders at https://calendly.com/ty-passo/30min, or connect the MCP server to start exploring the tools right away.