Setup guide · about 2 minutes

Connect your wallet to Claude.

One URL, with your token already inside it. You pick the fields, set an expiry, and paste it into Claude once. Claude reads only what you approved — and every read writes a receipt you can see and revoke.

What you're actually connecting.

ContextPass gives Claude a private connector to your wallet over MCP (the open Model Context Protocol). It's not a login, and it's not your whole wallet — it's a snapshot of the specific fields you choose, scoped to one assistant, that you can switch off the instant you want to.

  1. 1

    Mint a Claude connector in your wallet

    Open your wallet and click + Add new connector. Choose Claude as the assistant, tick the sections it's allowed to read (size, budget, style — only what you want), and set how long the connector lasts.

    You'll get back a single URL that looks like this:

    https://api.contextpass.io/mcp/u/<your-token>
    Copy it now — it's shown only once. Your access token lives inside the URL; nothing is stored in plaintext on our side. Lose it and you simply revoke the connector and mint a new one.
  2. 2

    Add it to Claude as a custom connector

    In Claude (browser, desktop, or mobile), open your settings and go to:

    Customize› Connectors› +› Add custom connector

    Paste the whole URL into the server-URL field and click Add. You don't need the Advanced / OAuth settings — your token is already in the URL.

    Custom connectors work on Free, Pro, Max, Team, and Enterprise plans. (Free is limited to one custom connector. On Team/Enterprise, an owner may need to add it org-wide first, then you click Connect.)
  3. 3

    Turn it on in a conversation

    In any chat, click the + in the message box, choose Connectors, and toggle ContextPass on. Claude can now read your scoped fields when it's helpful.

  4. 4

    Use it — just ask

    Claude pulls your context only when the conversation calls for it. Try:

    You "I'm shopping for running shoes — use my ContextPass details so you don't have to ask my size and budget."

    Behind the scenes Claude calls read for the fields it needs (and list_share_settings to see what's in scope). It never receives anything outside the consent you granted.

  5. 5

    Watch every read — and revoke any time

    Each read shows up in your wallet's audit feed: which assistant, which fields, when. Changed your mind? Revoke the connector in one click and the next read is blocked instantly — no waiting, no support ticket.

What Claude can and can't see.

Scoped to consent
Claude reads only the fields you ticked when you minted the connector. It can never widen its own access.
A snapshot, not your live wallet
Reads hit a snapshot that refreshes when you save your wallet. Your live wallet is never opened on the request path.
Receipted
Every successful read writes an auditable receipt. Rejected reads from a revoked connector are logged too.
Revocable & expiring
Connectors carry an expiry and a kill switch. Revoke once and it's dead everywhere, immediately.

Ready to connect?

Mint your Claude connector in under a minute. You choose the fields. You hold the kill switch.

Mint your connector → See the live demo

Using ChatGPT or another MCP client instead? The same /mcp/u/ URL works anywhere custom MCP connectors are supported — pick that assistant when you mint, and paste the URL into its connector settings.