How to connect Claude to your AI Passport

AI Passport lets Claude use selected personal context that you have approved and allowed it to read. The same Passport can supply context to another permitted assistant, so you do not have to maintain the same preference separately in each tool.

Start by connecting Claude to the correct Passport account. Then test one harmless preference in a fresh conversation.

1. Open the AI Passport connector listing

Use the AI Passport listing in Claude’s connector directory. You can also find connectors through Claude’s current Customize surface.

Review the integration, choose Connect and follow the authentication prompts. The Claude connector guide explains the current setup and organisational controls.

If you are in a managed workspace, check that your organisation permits the connection. The presence of a directory listing does not itself establish workplace approval.

Use the published listing for the normal hosted setup. A custom connector URL is a separate deployment route, not something you need to invent to complete this guide.

2. Choose the Passport account and access

Sign in during the Passport handoff. If you want to share context with ChatGPT, connect Claude to the same Passport owner account.

Read any category choices shown during memory consent. Selected categories can receive continuing, revocable recall access for this particular Claude connection.

Choose categories for the tasks you intend to do. A writing preference does not require every category you have saved.

After connecting, you can inspect the resulting passes in Passport. You use your own signed-in browser session to review proposals and permissions. Claude does not make those owner decisions for you.

3. Tell Claude where you want memory saved

Claude has its own memory system. Name AI Passport explicitly when you want a statement saved there.

Use AI Passport to propose this preference. For routine explanations, begin with a concrete example and then explain the general idea.

The current Claude directory integration does not bundle the same Passport routing skill as the ChatGPT plugin. A short instruction can help with repeated use.

When I ask to save something to AI Passport, use its connector and tell me the returned review state. Retrieve Passport context when I ask for it.

Put suitable guidance in Claude’s available instructions or the relevant project’s instructions. It can influence the tool Claude chooses, but it cannot grant missing access.

4. Review the proposed statement

Open your Passport Inbox and find the proposal. In the normal review-first flow, it stays pending until you approve it.

Check that it preserves the scope of your request. “Start routine explanations with an example” is different from an instruction never to provide a detailed analysis.

Correct the wording before approval if necessary. Approving a statement makes it an approved memory; allowing a particular app to read the relevant category is a separate permission.

You may already have granted suitable category access during connection. A later recall does not necessarily require another approval screen.

5. Test recall in a fresh chat

Start a new Claude conversation and ask it to retrieve the saved preference.

Use AI Passport to retrieve my explanation preferences. Tell me what it returned. Then explain how a weather forecast differs from a climate average using that preference.

Read any permission request and check the actual access involved. If recall succeeds, compare the returned statement with what you approved.

You can test shared memory by saving another harmless preference through a different connected assistant, reviewing it in Passport and requesting it through Claude. The useful result is one accurate statement travelling between permitted tools.

Fix the stage that failed

If Claude cannot find Passport tools, check the connector’s status and refresh the integration if needed. Start a new conversation after reconnecting.

If a save went to Claude’s native memory, name Passport in the request and check that a proposal appears in your Passport Inbox.

If recall is empty, check approval and the connected account before saving another copy. A permission request or a temporary outage is not evidence that the memory disappeared.

Live app data is separate. To use a calendar or another available source through Passport, link that source and review Claude’s exact source access when requested. Connecting the assistant alone does not complete that step.

Review test passes when finished. Revocation controls future reads under those passes. An earlier Claude conversation may still hold information it received, so manage that copy through Claude’s own controls when necessary.

Read about Passport’s owner review and access model.