MultiPass keeps your memory, profile, and connected tools (Notion, email, calendar, GitHub, Slack) behind one URL. Paste it into any MCP-enabled AI and it knows you. Hit a cap, switch providers. Go local when it's private. Leave whenever. The context comes with you.
01 /Why MultiPass
Tuesday, mid-task: Claude tells you to come back Thursday. Or ChatGPT closes the session at the worst possible moment. The work didn't pause. The quota did.
Open another provider, or your second account, and pick up the exact thread. Same memory, same context. The new session already knows where you were, because your memory never belonged to the app that stopped.
Health. Legal. Money. Family. Some conversations shouldn't travel to a data center, but the model that stays home shouldn't have to meet you as a stranger.
Run a private model on your own machine, with your full memory and profile. Private and personal at the same time. You were never supposed to choose. When the heavy reasoning calls, swap back to a frontier model without skipping a beat.
Claude keeps one memory of you. ChatGPT keeps another. Each lives on that vendor's servers, on that vendor's terms, and the longer you stay, the more it costs to go. That isn't loyalty. It's leverage.
Move whenever you like: cancel a subscription, try the new model, run two side by side. A model you've never used knows you on day one.
02 /How it works
You get your own context behind one URL, encrypted with your own key and stored in the EU.
Notion, email, calendar, GitHub, Slack. Each one a scoped tool you can revoke as fast as you added it.
Into Claude, ChatGPT, Cursor, a local model. One consent screen later, it knows you. All of them do.
03 /Connectors
Each connector is a live bridge to a source you already use, handed to your AIs as scoped, revocable tools.
Scope-gated: an assistant only reaches what you grant · More on the way
04 /The sensitive vault
Health. Legal. Family. Residency. Memory you mark as sensitive stays out of reach until you grant an AI the separate sensitive permission, per client. Like the rest of your context, it is encrypted with your own key.
When an AI connects, you see exactly what it asks for, and exactly what it doesn't get. A coding assistant has no business knowing your medical history. So it doesn't.
Vault categories: health · legal · family · residency
Consent: one sensitive permission, per client · revocable anytime
multipass.host/consent
Claude wants to connect
05 /Open protocol
PCP, the Portable Context Protocol, is an open, vendor-neutral protocol developed in public by its contributors in the pcp-protocol organization. It is independent of Phantazein: no company owns it, and no implementation is the official one. MultiPass is one business built on top of it, a hosted PCP server run by Phantazein. If it ever stops earning your trust, the open format is designed so you can move your context to any other PCP server, built by anyone on the open spec.
MultiPass is also a worked example of how a business can be built on an open protocol. The protocol stays free and portable; the business earns its keep with what goes around it.
Format, discovery, consent scopes, export. Public and identical for every implementation, so users can always leave.
What a host adds on top: user-held keys, EU storage, a control panel, onboarding, support. This is where a business competes.
Host contexts, build a client, an importer, or a connector. The spec is open to anyone, free of charge, for any purpose.
06 /Questions
Exactly what the consent screen shows. Memory and profile by default; connected sources if you allow them; sensitive memory only if you grant that permission explicitly. Every scope is revocable, per client, at any time.
Portable Context Protocol: an open protocol for serving personal context over MCP. It is developed in the open in the pcp-protocol organization, independent of Phantazein, and the spec is public under Apache 2.0. MultiPass is one hosted PCP server; because the spec is open, anyone can build another that does the same.
Not yet: export is being built now. It will produce a complete archive of your memory and profile in the open PCP format, encrypted by default, that any PCP server can import. No proprietary blobs.
Your data is stored in the EU. Requests from your AI tools are handled on our provider's global network and may be processed outside the EU, close to where those tools run. We can't read your context at rest, in backups, or without a connector you have authorized. It is decrypted only in memory, only while a connector you approved is making a request, and every access appears in your audit log. Every account has its own key, so accounts are cryptographically isolated from each other.
Anything that speaks MCP: Claude, ChatGPT, Cursor, and local models through an MCP client. Paste your URL, pass one consent screen, and the tool has your context.
Nothing. MultiPass is in early beta: accounts are free and by invitation, for early beta users. Join the waitlist and we open accounts in small batches, oldest signups first.
07 /Get started
Your memory is the story you keep telling yourself about who you are. Lately you've been telling parts of it to machines you don't own. Keep the original: portable, shared scope by scope, on an open protocol anyone can implement.