Start solo. Add workspace controls later.

Every AI integration. One Passport.

Browse apps, add an AI client, then run passport login to activate a profile or paste your connector URL. Credentials, workspace policy, and Activity stay in one place.

Free for up to 5 members and 5 connected MCPs · No card required
Web and CLI first. Desktop when useful.Live workspace
Your AI clients Claude Cursor Codex
Passport Credentials stay here
Your MCPs GitHub Notion Linear
Connect accounts onceUse approved tools anywhereRevoke from one place

Simple for one person. Ready for the whole company.

Start with the workflow you need today. Add shared controls without asking people to abandon the AI clients they already use.

For developers

Connect once. Work anywhere your agent runs.

Move between Windows, Linux, macOS, chat, editor, terminal, and CI without rebuilding every integration.

  • Windows and Linux: web install hub, native MCP, and Passport CLI
  • Secretless browser OAuth where the client supports it
  • Optional macOS app to wire several local clients at once
Create workspace
For IT and security

Make AI access useful, visible, and revocable.

Give teams approved access without spreading credentials and policy across every AI vendor.

  • Discover direct MCPs already configured in supported desktop clients
  • Team controls, central offboarding, and attributable governed activity
  • OIDC SSO, SCIM, SIEM export, and self-hosting
Explore Enterprise

Bring your MCPs. Keep your stack.

Start with popular connectors out of the box, or add any remote MCP. Enterprise workspaces can require review and control rollout by team.

Browse the catalog →

See Passport in action

A solo developer connects GitHub, adds Passport CLI, and runs the built-in read-only setup check. Enterprise policy and team rollout stay available when the workspace grows.

Passport
Maya · Apps
GitHubPersonal account Connected
Browse apps → Connect read-only first
1Browse appsMaya connects the account she wants to use.
2Add a clientRun passport login to activate a profile, or paste the connector URL.
3Prove the pathA safe diagnostic crosses policy and lands truthfully in Activity.
Passport admin audit log of governed MCP calls: allowed GitHub, Slack, and Notion reads, two write actions blocked by policy, each attributed to a named person and their AI client (Cursor, ChatGPT, Claude).
The admin audit view: every governed call attributed to a person and the AI client they used.
Connect, govern, audit.

Protect access without slowing people down.

AI clients receive scoped Passport access. Upstream credentials stay encrypted at the gateway and out of client configuration files.

Credentials protectedUpstream OAuth tokens and company keys are encrypted at rest with AES-256-GCM.
Access matched to the jobChoose what each workspace, team, person, client, and governed tool can use.
Offboarding from one placeRevoke sessions, clients, and connected-account grants centrally or through SCIM.
Useful activity, less sensitive contentAttribute governed calls without storing prompts, full arguments, or tool results in the audit trail.

Prefer your own VPC? Run Passport as one container plus Postgres, with the same gateway and catalog.

Review the full security posture →

Built in the open

Passport is in early access. Review the live catalog, dated changelog, status page, and security posture, including what we haven't earned yet.

Free for 5 members Pro $15/member/month Enterprise $30/member/month Self-host See pricing →

Connect your MCPs once.

Start free. Add workspace controls when your team needs them.