Build with Passport.Me
One OAuth consent, then any Model Context Protocol agent reads your users' Gmail, Calendar, Drive, Docs, Sheets, Contacts, and portable AI memories. Read-only unless the user opts in to writes.
- Endpoint
https://mcp.passport.me/mcp- Transport
- Streamable HTTP
- Auth
- OAuth 2.1 · PKCE · DCR
- Scope
- passport.mcp · passport.mcp.write
- Access
- Read · opt-in write
Add Passport.Me to your agent
MCP clients register automatically via dynamic client registration. Point them at the endpoint and approve the consent screen.
Claude
- Settings → Connectors → Add custom connector.
- Paste
https://mcp.passport.me/mcp. - Approve the Passport.Me consent screen.
ChatGPT
- Settings → Connectors → add an MCP server.
- Paste
https://mcp.passport.me/mcp. - Approve consent, then call tools in chat.
Cursor / custom clients
- Register via DCR:
POST https://passport.me/.register - Run the authorization-code + PKCE flow against
/oauth/authorizeand/oauth/token. - Call
https://mcp.passport.me/mcpwithAuthorization: Bearer.
CLI
npm install -g @passportme/clipassportme loginpassportme mcp config --format claude
What an agent can read — and write
After consent, these tools are callable against the MCP endpoint. Visibility reflects what each user has connected; write tools appear only when the user has granted write access.
| Category | MCP tools |
|---|---|
| Gmail | search, fetch, email_search, receipt_search, email_open |
| Calendar | calendar_upcoming |
| Drive · Docs · Sheets | drive_find, doc_read, sheet_read |
| Contacts | contacts_list |
| Wallet | wallet_portfolio, wallet_recent_activity, wallet_nfts, wallet_defi_positions |
| Memories · Profile | ai_memories, demographics, passport_profile_facts |
| GitHub · Oura · Spotify | github_user, github_repos, github_starred, github_issues, github_repo_detail, oura_personal_info, oura_daily_sleep, oura_daily_activity, oura_daily_readiness, oura_sleep_periods, oura_workouts, spotify_top_tracks, spotify_top_artists, spotify_recently_played, spotify_playlists, spotify_saved_tracks |
| Write (opt-in) | sheet_create, sheet_append, add_tab, duplicate_sheet, doc_create, doc_append |
| Sensitive write (opt-in) | calendar_create_event, calendar_update_event, calendar_delete_event, sheet_write, drive_trash |
passport.mcp. Writes need the opt-in passport.mcp.write scope plus the user's per-app switch, and are limited to Sheets, Docs, Calendar and Drive trash — Gmail, Contacts and wallets stay read-only. A write that edits anything the app didn't create, trashes a file, sends invitations, or lands on a calendar other than the user's primary one returns a preview and a confirmation_token first, and runs only after the user approves it on Passport.Me. Every call is logged to the user's activity feed and any app can be disconnected in one click.
Machine-readable everything
Every integration detail is published as a standard document. Fetch these directly — no account required.
OpenAPI 3.1
Full API surface for GPT Actions, Dify, and importers.
MCP server card
Self-describing tool + data-source surface.
API catalog
RFC 9727 linkset of every machine endpoint.
OAuth authorization server
Endpoints, grant types, PKCE, supported scopes.
OAuth protected resource
RFC 9728 metadata for the protected MCP surface.
Agent skills
Connect + markdown-negotiation skill docs.
llms.txt
Curated, link-rich index for LLM agents.
llms-full.txt
Expanded documentation in a single fetch.
ai-plugin.json
Plugin manifest for GPTs and agent runtimes.
Find Passport.Me in MCP directories
Passport.Me is listed as me.passport/mcp in the official MCP Registry, and directories that read the registry pick it up from there.
Building an MCP directory or agent platform? Our server card at /.well-known/ describes every tool.