Skip to main content
This is the shortest path from sign-in to a working agent. It works on Windows, Linux, and macOS.

​
1. Sign in

Open your invite, or sign in at passportmcp.com. If your company uses single sign-on, Passport will send you to your company’s sign-in page. After signing in, you should see Apps, Agents, Activity, and Settings.

​
2. Connect a work app

Open Apps.
  • Choose an app you already have access to and select Connect.
  • Complete the provider sign-in in the Passport Connect window.
  • If your workspace requires approval or company setup, Passport shows that instead of pretending the app is ready.
Your provider credentials stay in Passport. They are not copied into Claude, Cursor, ChatGPT, Codex, or another agent.

​
When your agent asks you to connect again

If an app was never connected—or its sign-in expired—Passport can now let your AI agent show the next step right where you are working.
  • Some agents show a built-in Connect or Reconnect action.
  • Other agents show a secure Passport link in the conversation.
  • Open the link, confirm that it uses your Passport domain, and finish the provider sign-in in your browser.
  • Return to the agent when Passport says All set. The agent can retry the original task; it never receives your provider password or token.
The link is short-lived and tied to your Passport account. Another signed-in person cannot use it to connect their account on your behalf.

​
3. Add your agent

Open Agents, choose Add agent, then pick where you want to use Passport. Passport shows current instructions for each agent:
  • Cursor and VS Code have one-click setup.
  • Claude Code and Codex use their own MCP command and browser sign-in.
  • Claude Desktop, Claude.ai, and ChatGPT use the connector address Passport gives you.
  • Terminal agents can use Passport CLI. Scripts and CI use an automation key from Agents → Automations.
  • Other agents can copy the advanced connector address if they support remote MCP and browser sign-in.
Follow the steps in Passport and finish the browser sign-in. No provider token should be pasted into your agent.
Setting up several agents on one computer? npx passport-bridge@latest init adds Passport to each of them in one pass. If an agent’s browser sign-in cannot reach a localhost, private, or self-hosted Passport server, choose Local bridge in its setup instead.

​
4. Confirm the connection

Keep the agent open and ask:
List my available Passport tools.
In the setup guide, choose Test connection. Passport waits for the agent’s first request, then says what it can reach, such as “Claude Code can see 13 apps and 172 tools”. You can run the same test later from the agent’s page in Agents. Then choose Run setup check in the checklist. The check is safe, does not contact the app provider, and opens Activity so you can see the result. If the test keeps waiting, finish the sign-in inside the agent, keep it open, and test again. See Troubleshooting for common fixes.

​
Make it yours

  • Open a connected agent and use Limit apps for this agent to hide apps it does not need.
  • Open Safety preferences to ask before write or destructive actions.
  • Open Activity to review what your agents did and whether Passport allowed, blocked, or failed the action.

Passport CLI

Use Passport from a terminal agent, script, or CI job.

Troubleshooting

Fix sign-in, missing apps, or a duplicate compatibility connection.