Not for the guided Claude, ChatGPT, or Cowork paths. Claude Code, Codex, OpenClaw, and generic MCP setups are more technical and list their prerequisites before you start.

Yes. Disconnect or remove the connection in the host, and revoke authorization if needed. That stops future access. Memories already stored stay in your vault until you delete them.

MemoryRouter for your AI tools

One MCP memory server. Every compatible AI.

Q: What is MCP in normal language?

MCP is a standard way for an AI app to use an outside tool. Here, the tool is MemoryRouter. The connection lets the AI search or save the vault you approve. You do not need to understand the protocol to use a supported setup.

Q: Does connecting MemoryRouter copy all my old chats?

No. Connection enables future memory access. It does not read or import your old conversations. Use the Basic transfer to move what ChatGPT remembers about you today, or the Advanced import for your full export.

Q: Can MemoryRouter read everything in my AI account?

No. The connector receives only the arguments a host sends to an approved MemoryRouter tool. It does not receive your password, cookies, email, or a bulk copy of private account history.

Q: Which option is easiest?

For a normal Claude user, start with the guided custom connector. For ChatGPT, turn on Developer mode. For local coding work, use the published hook package for your coding agent.

Q: Which ChatGPT plans support the connector?

Plus, Pro, Business, Enterprise, and Education on ChatGPT web. Developer mode is the setup path; MemoryRouter is not listed in the ChatGPT Plugin directory. In managed workspaces an admin enables Developer mode.

Q: How do I know the connection is being used?

A connected badge shows authorization succeeded. A visible MemoryRouter tool result in the chat shows memory was actually used. Ask for memory_status any time to see both.

Q: Can I use read-only access?

Where the host and current MemoryRouter install method expose a read-only grant, yes. Read-only must be enforced by OAuth scope or server policy, not merely by instructions in a skill.

Connect MemoryRouter to Claude, ChatGPT, Cowork, Claude Code, Codex, OpenClaw, and compatible MCP clients. Choose a vault and permissions once, then every connected AI searches and saves the same memory.

Connect MemoryRouter via MCP Move what ChatGPT remembers about you

Want exact details from years of old conversations? Use Advanced import.

Compatibility reviewed 2026-08-06; live MCP endpoint verified 2026-08-05.

You choose the vault. You approve the permissions. Your memory stays yours.

You approve a durable memory

Your MemoryRouter vaultOne selected vault

ClaudeConnector tools

ChatGPTConnector tools

Coding agentsAutomatic hooks

One vault. Every AI you use.

Your first cross-AI win

Carry one approved memory from ChatGPT into Claude.

Connect both to the same vault, move what ChatGPT remembers about you, then watch Claude pick up exactly where ChatGPT left off.

First-run successClaude recalls one reviewed detail from ChatGPT through MemoryRouter and continues the work.

Connect MemoryRouter in ChatGPT.
Search and save portable memory from ChatGPT through Developer mode. Two minutes in Developer mode.
Check: Ask ChatGPT to run MemoryRouter memory_status. The tool result appears in the chat.
View ChatGPT setup
Move what ChatGPT remembers about you.
Run the reviewed transfer prompt, read every fact ChatGPT knows about you, remove anything you want left behind, then save the version you approve.
Check: Search MemoryRouter for one approved profile detail before moving to Claude.
Open the transfer workflow
Review and connect MemoryRouter in Claude.
Use one selected MemoryRouter vault from Claude web, desktop chat, or mobile chat. Choose the same MemoryRouter vault you used in ChatGPT so your memory has one home.
Check: Claude shows MemoryRouter as available for the conversation and runs memory_status.
Review and connect
Prove continuation in Claude.
Ask Claude to recall one detail from the transfer through MemoryRouter, then keep working from it. Claude picks up exactly where ChatGPT left off.
Check: Claude returns the approved detail through a visible MemoryRouter tool result and uses it in the next response.
See the verification sequence

Want the exact details from years of old conversations? Use the official export with Advanced import.

Choose your AI

Start where you already work.

Every platform reaches the same MemoryRouter vault through its own setup. Each card shows the exact steps, plan, and permissions before you connect.

Guided connections

Start in the app you already use. Connect once, then ask your AI to remember or recall anything.

Use one selected MemoryRouter vault from Claude web, desktop chat, or mobile chat.

Best for: People who want portable memory in hosted Claude chat.
Setup: Custom connector + OAuth
Difficulty: Easy
Required plan/app: Claude account; Free supports one custom connector
Memory behavior: Connector tools the AI calls in chat
Permissions: OAuthReadWriteMemoryRouter OAuth. No Memory Key is entered in the host.
Old conversations: Memory starts the day you connect

Review and connect

Opens a prefilled connector in Claude. Sign in, choose a vault, approve access.

Claude setup details

Prerequisites

Claude account; Free supports one custom connector
MemoryRouter account with at least one vault
Organization policy may require an Owner or Primary Owner to add/allow the connector

Verify

Confirm Connected in Customize > Connectors
In a new chat, explicitly ask Claude to run memory_status

Upgrade and remove

Hosted connector uses the live service; refresh or reconnect after material metadata changes
Disconnect MemoryRouter in Claude
Remove the custom connector if desired; stored vault memories are not deleted

Search and save portable memory from ChatGPT through Developer mode.

Best for: ChatGPT users who want their memory to travel to Claude and every other AI.
Setup: Developer mode connector
Difficulty: Moderate
Required plan/app: ChatGPT Plus, Pro, Business, Enterprise, or Education web account
Memory behavior: Connector tools the AI calls in chat
Permissions: OAuthReadWriteMemoryRouter OAuth. No Memory Key is entered in the host.
Old conversations: Basic transfer or Advanced import from your official export
Host directory: not listed

View ChatGPT setup

Opens the step-by-step ChatGPT Developer mode guide.

ChatGPT setup details

Prerequisites

ChatGPT Plus, Pro, Business, Enterprise, or Education web account
Developer mode enabled in Settings under Security and login
In managed workspaces, an admin enables Developer mode

Verify

Enable MemoryRouter in a new conversation
Explicitly call memory_status and a read test before enabling writes

Upgrade and remove

Refresh/recreate the developer connection after metadata changes
Disable or remove the developer connection; vault data remains

Use MemoryRouter tools in Cowork tasks and optionally add behavioral skills/plugins.

Best for: Paid-plan Cowork users who want guided recall and deliberate saves.
Setup: Custom connector; optional package
Difficulty: Easy
Required plan/app: Paid Claude plan with Cowork access
Memory behavior: Connector tools the AI calls in chat
Permissions: OAuthReadWriteMemoryRouter OAuth. No Memory Key is entered in the host.
Old conversations: Memory starts the day you connect
Host directory: not listed

Open Cowork setup

Opens the guide: add the connector, sign in, enable it for your task.

Claude Cowork setup details

Prerequisites

Paid Claude plan with Cowork access
MemoryRouter account with at least one vault
Organization policy can require Owner or Primary Owner enablement

Verify

Call memory_status and verify the selected opaque vault reference
Test an explicit recall and an explicitly approved save

Upgrade and remove

Reconnect after scope changes
Replace the optional ZIP with a newer validated version
Disconnect/remove the connector and optional artifact; vault data remains

Automatic local integrations

One command installs hooks that recall before every prompt and capture at the end of every turn.

Automatic project recall and capture through local lifecycle hooks, plus optional MCP tools.

Best for: Developers who want cross-session project memory.
Setup: Published npm hooks package
Difficulty: Technical
Required plan/app: Node.js 18+
Memory behavior: Automatic hooks on every turn
Permissions: ReadWriteA local Memory Key powers hooks; optional MCP uses OAuth.
Old conversations: Memory starts the day you connect

Install for Claude Code

Opens the install guide. One command wires the hooks with your Memory Key.

Claude Code setup details

Prerequisites

Node.js 18+
Claude Code installed and signed in
MemoryRouter Memory Key for automatic hooks

Verify

npx -y memoryrouter-claude doctor
Start a new same-project session and verify recalled context

Upgrade and remove

npx -y memoryrouter-claude init
npx -y memoryrouter-claude off
npx -y memoryrouter-claude off --purge

Automatic project recall/capture with local hooks and explicit MCP tools.

Best for: Codex CLI, IDE, and local-host users in trusted projects.
Setup: Published npm hooks package
Difficulty: Technical
Required plan/app: Node.js 18+
Memory behavior: Automatic hooks on every turn
Permissions: ReadWriteA local Memory Key powers hooks; remote MCP uses OAuth.
Old conversations: Memory starts the day you connect

Install for Codex

Opens the secure local install guide.

OpenAI Codex setup details

Prerequisites

Node.js 18+
Codex 0.145+ for full hooks; 0.146+ for current remote OAuth
MemoryRouter key for hooks

Verify

npx -y memoryrouter-codex doctor --scope user
Start a new trusted-project session and verify recall

Upgrade and remove

npx -y memoryrouter-codex init --scope user
npx -y memoryrouter-codex uninstall --scope user

Automatic relay-based recall/capture plus optional historical workspace/session upload.

Best for: OpenClaw operators who want automatic agent memory.
Setup: Published npm plugin
Difficulty: Technical
Required plan/app: Current OpenClaw
Memory behavior: Automatic hooks on every turn
Permissions: A Memory Key stays in the local plugin configuration.
Old conversations: Upload prior workspace and session history with openclaw mr upload
Host directory: unverified

Install for OpenClaw

Opens the one-command npm install guide.

OpenClaw setup details

Prerequisites

Current OpenClaw
npm/network access
Explicit trust for the third-party npm source
MemoryRouter key

Verify

openclaw mr status
openclaw plugins inspect mr-memory --runtime --json

Upgrade and remove

openclaw plugins update mr-memory
openclaw mr off
openclaw plugins uninstall mr-memory

Advanced connection

Bring any MCP client that supports remote Streamable HTTP and OAuth.

Connect any compatible remote MCP client to one MemoryRouter vault.

Best for: Advanced users bringing their own MCP client.
Setup: Client-specific remote MCP setup
Difficulty: Advanced
Required plan/app: Client supports remote Streamable HTTP MCP
Memory behavior: Connector tools your client calls
Permissions: OAuthReadWriteMemoryRouter OAuth. No Memory Key is entered in the host.
Old conversations: Memory starts the day you connect

Read generic MCP setup

Opens the setup instructions and the connector address.

Other MCP clients setup details

Prerequisites

Client supports remote Streamable HTTP MCP
Client supports RFC 9728 OAuth discovery and an OAuth callback flow
Client can expose the needed tools/resources and scopes

Verify

Run memory_status if the client exposes it
Test read before requesting write or delete scopes

Upgrade and remove

Refresh/reconnect according to the client after service metadata changes
Disconnect/remove the MCP server from the client; vault data remains

Live hosted service

One endpoint. Five explicit memory tools.

The public endpoint uses remote Streamable HTTP. A live server/discover check on August 8, 2026 returned HTTP 200, server version 1.1.0, and the current protocol revisions.

Remote MCP endpointhttps://mcp.memoryrouter.ai/mcpVerified 2026-08-05 · stateless · Streamable HTTP

search_memoriesmemories:read

Search the selected vault by meaning.

store_memorymemories:write

Save one concise, explicitly approved durable memory.

memory_statusmemories:read

Confirm the connection, opaque vault reference, counts, and granted scopes.

forget_all_memoriesmemories:delete

Delete the entire selected vault only after separate authorization and exact confirmation.

searchmemories:read

Compatibility alias for clients that require a tool named search.

Architecture

How the MCP memory server works.

ClientA compatible host connects to the exact remote endpoint and follows OAuth discovery.
AuthorizationOAuth with PKCE binds that connection to one selected vault and independent read, write, or delete scopes.
VaultThe tools search or change only the selected MemoryRouter vault. Switch vaults by disconnecting and reconnecting.
Host behaviorClaude and ChatGPT call the connector tools in chat. Claude Code, Codex, and OpenClaw add automatic hooks that run on every turn.

Basic or Advanced

Two ways to move your ChatGPT context.

Start with the 2-minute memory transfer, or recover the exact details from your official export.

Basic · about 2 minutes

Move what ChatGPT remembers.

Pull what ChatGPT remembers about you into a structured profile, review every line, then save what you approve. About 2 minutes.

Available nowStart the Basic transfer

Advanced · official export

Want the exact details from years of old conversations?

Use your official ChatGPT data export with the deterministic local importer. Preview supported records, approve one exact digest, resume or cancel safely, and keep a reconciled receipt.

Available nowOpen the Advanced guide

A visible trust boundary

Connect without handing over your account.

MCP is only the connector under the hood. You stay in control of the host, selected vault, and requested permissions.

Pick a supported AI.
Use the chooser to see the real setup, plan, and capture behavior.
Check: The card matches the exact host and surface you intend to use.
Review access.
Sign in to MemoryRouter, choose one vault, and approve only the permissions the connection requests.
Check: The host shows the expected MemoryRouter connection and selected vault boundary.
Verify a real tool call.
Ask for memory status, then test a recall or an approved save. The tool result appears right in the chat.
Check: A visible MemoryRouter tool result appears in the conversation.

Prove the connection

A connected badge is only step one.

Follow the trail from setup to a visible MemoryRouter result in your chat.

Open setup

Start from the platform card and read the exact boundary.

Review endpoint

https://mcp.memoryrouter.ai/mcp

Choose a vault

Select one vault during MemoryRouter authorization.

Review permissions

Treat read, write, and destructive access as separate capabilities.

Verify status

Ask the AI to run MemoryRouter status.

Verify across an AI

From another connection to the same vault, explicitly recall one approved fact.

Connected is step one. Seeing your memory show up in the chat is the win.

Privacy and permissions

You choose what crosses the boundary.

A normal MemoryRouter connection does not receive your ChatGPT history, browser cookies, email, password, or every file on your device. OAuth binds the connection to one MemoryRouter vault you select. The host can use only the tools and permissions granted to that connection. Disconnect any time; your memories stay in your vault.

What MemoryRouter does not get

No account password. No browser cookies. No mailbox access. No hidden ChatGPT memory database. No automatic permission to old conversations. Old conversations move only through the import tool, from the official export file you choose, with your approval.

RRead: Search and inspect memory in the selected vault.
WWrite: Save explicitly requested or approved durable memory. A write grant is separate from read.
!Destructive controls: Require separate authorization and explicit confirmation. Use the MemoryRouter dashboard for individual memory review and curation.
FFiles: A connector never gets general device access. Cowork or a local coding agent reads only the files or folders you grant through that host.
×Revocation: Disconnect the host or revoke the MemoryRouter authorization. Stored vault data remains until the user deletes it separately.

Connect versus import

Know which promise you are choosing.

Connect for everything going forward. Transfer or import for everything that came before.

Compare connecting future memory, quick transfer, and complete import
Question	Going forwardConnectAvailable now	Basic · about 2 minutesBasic transferAvailable now	Advanced · official exportAdvanced importAvailable now
Main purpose	Recall and save from today forward	Portable profile now	Exact history recovery
Source	Your conversations in the connected AI	What ChatGPT remembers about you	Your official ChatGPT export
How it runs	Automatic hooks in Claude Code, Codex, and OpenClaw; connector tools in Claude and ChatGPT	You run one reviewed prompt	You launch the local importer after a preview
Covers	Everything from the day you connect	Your profile, preferences, and working context	Every supported message in the export, with a report of anything skipped
Review before write	You approve saves in chat	You approve every line	Preview and exact approval digest
Resume and cancel	Not needed	Not needed	Built in
Receipt	Tool result in the chat	Verify with one search	Reconciled import receipt

Going forward

Connect

Give a supported host access to one selected MemoryRouter vault.

Available now

Main purpose: Recall and save from today forward
Source: Your conversations in the connected AI
How it runs: Automatic hooks in Claude Code, Codex, and OpenClaw; connector tools in Claude and ChatGPT
Covers: Everything from the day you connect
Review before write: You approve saves in chat
Resume and cancel: Not needed
Receipt: Tool result in the chat

Choose your AI

Basic · about 2 minutes

Basic transfer

Move what ChatGPT remembers into a reviewed portable profile in about 2 minutes.

Available now

Main purpose: Portable profile now
Source: What ChatGPT remembers about you
How it runs: You run one reviewed prompt
Covers: Your profile, preferences, and working context
Review before write: You approve every line
Resume and cancel: Not needed
Receipt: Verify with one search

Use the reviewed prompt

Advanced · official export

Advanced import

Recover supported exact details from years of old conversations with deterministic preview, approval, resume, cancellation, and reconciliation.

Available now

Main purpose: Exact history recovery
Source: Your official ChatGPT export
How it runs: You launch the local importer after a preview
Covers: Every supported message in the export, with a report of anything skipped
Review before write: Preview and exact approval digest
Resume and cancel: Built in
Receipt: Reconciled import receipt

Use the Advanced importer

Troubleshooting

Verify the vault, scope, then tool call.

Most setup issues are a missing OAuth grant, the wrong selected vault, or a turn where the AI was not asked to check memory.

The client says authentication is required.

That is expected on first use. Complete the MemoryRouter OAuth flow, select one vault, then retry the tool call.

A save or delete is refused.

Read, write, and delete are independent scopes. Reconnect and approve the missing scope instead of retrying an under-scoped token.

Recall returns nothing.

Run memory_status and check the vault reference. Reconnect to the vault that holds the memory.

Claude or ChatGPT skipped memory on a turn.

Ask it directly to check MemoryRouter. The tool result appears right in the chat.

Read the complete MCP troubleshooting guide

Pricing

$20 a month after a 14-day trial.

One plan includes every MemoryRouter integration: Claude, ChatGPT, Cowork, Claude Code, Codex, OpenClaw, and any compatible MCP client. Enterprise and shared-team use have a separate path.

Pricing verified against the public pricing page on August 8, 2026.

Start the 14-day trial Review pricing and usage Explore Enterprise

Questions, answered plainly

What connection actually means.

No protocol lesson required. Just the boundaries that matter before you connect.

What is MCP in normal language?

Does connecting MemoryRouter copy all my old chats?

Can MemoryRouter read everything in my AI account?

Do I need to code?

Which option is easiest?

Which ChatGPT plans support the connector?

How do I know the connection is being used?

Does every platform save memory automatically?

Claude Code, Codex, and OpenClaw use automatic hooks: recall runs before every prompt and capture runs at the end of every turn. Claude, ChatGPT, and Cowork use connector tools, which means the AI calls MemoryRouter when you ask it to or when it decides memory is relevant, so it is not guaranteed on every turn. Ask directly and you get a visible tool result. None of the hosted connectors sync your full transcript.

Can I use read-only access?

Can I disconnect it?

Is this the same as ChatGPT Memory?

How do I move what ChatGPT remembers about me?

Does MemoryRouter work across Claude and ChatGPT?

Start where you already work

Choose one AI. Keep the same vault ready for the next.

See the real setup, permissions, and memory behavior before you connect.

Connect MemoryRouter via MCP Move what ChatGPT remembers about you

One MCP memory server. Every compatible AI.

Carry one approved memory from ChatGPT into Claude.

Connect MemoryRouter in ChatGPT.

Move what ChatGPT remembers about you.

Review and connect MemoryRouter in Claude.

Prove continuation in Claude.

Start where you already work.

Guided connections

Prerequisites

Verify

Upgrade and remove

Prerequisites

Verify

Upgrade and remove

Prerequisites

Verify

Upgrade and remove

Automatic local integrations

Prerequisites

Verify

Upgrade and remove

Prerequisites

Verify

Upgrade and remove

Prerequisites

Verify

Upgrade and remove

Advanced connection

Prerequisites

Verify

Upgrade and remove

One endpoint. Five explicit memory tools.

How the MCP memory server works.

Two ways to move your ChatGPT context.

Move what ChatGPT remembers.

Want the exact details from years of old conversations?

Connect without handing over your account.

Pick a supported AI.

Review access.

Verify a real tool call.

A connected badge is only step one.

Open setup

Review endpoint

Choose a vault

Review permissions

Verify status

Verify across an AI

You choose what crosses the boundary.

Know which promise you are choosing.

Connect

Basic transfer

Advanced import

Verify the vault, scope, then tool call.

The client says authentication is required.

A save or delete is refused.

Recall returns nothing.

Claude or ChatGPT skipped memory on a turn.

$20 a month after a 14-day trial.

Continue with the exact client guide.

What connection actually means.

Choose one AI. Keep the same vault ready for the next.