Cross-LLM memory without copy-paste
Share context between ChatGPT and Claude
ChatGPT and Claude do not share conversation history. A decision made in one chat is invisible to the other unless you paste it by hand.
Palim is a hosted MCP memory server both tools can connect to. You explicitly save the sessions or decisions worth keeping, then search and retrieve them from the other client with source and timestamp.
What you can move between ChatGPT and Claude
- Architecture and product decisions with reasoning
- Research notes from Perplexity or ChatGPT that Claude should continue
- Debugging discoveries and rejected approaches
- Preferences and standing rules you want both tools to respect
ChatGPT ↔ Claude in four steps
- 1
Connect ChatGPT
In ChatGPT: Settings → Apps → Advanced Settings → enable Developer Mode → Create app. URL: https://api.usepalim.com/mcp. Authentication: OAuth with OIDC disabled. In every chat, add Palim with @Palim.
- 2
Save useful context from ChatGPT
After a useful answer, ask Palim to save the session or one durable decision. Use terms you will search for later.
@Palim Save this decision to Palim with the alternatives we rejected and why. - 3
Connect Claude
In Claude, add a custom connector / remote MCP server with URL https://api.usepalim.com/mcp and finish OAuth. No API key is required for that flow.
- 4
Retrieve in Claude before you continue
Ask Claude to search Palim for the decision or topic before it drafts or plans further work.
Search Palim for the authentication architecture decision from ChatGPT and summarize what we chose.
Why ChatGPT Memory is not enough
ChatGPT Memory stays inside ChatGPT. It cannot hand a decision to Claude Desktop, Claude Code, or Cursor. Palim is the shared layer when you use more than one AI product.
You stay in control: nothing is imported unless a Palim save tool is called explicitly (or your client is configured to do so).
Honest setup notes
ChatGPT requires Developer Mode / custom apps on a plan that supports them, and OIDC must stay disabled or the OAuth flow fails. Claude Connectors use OAuth against the same MCP URL.
Search today uses full-text and text matching, not semantic embeddings — concrete keywords and tags work best.
- One hosted MCP endpoint for every client
- EU database region in Frankfurt
- AES-256-GCM for supported stored content fields
- Works with Cursor and Claude Code on the same account
Frequently asked questions
How do I share context between ChatGPT and Claude?
Connect both to Palim via MCP, save the useful context from one client, then search and retrieve it from the other. They do not sync chats automatically.
Does ChatGPT Memory sync to Claude?
No. ChatGPT Memory is locked to ChatGPT. Palim is a separate, cross-tool memory you control.
Do I need an API key?
Claude and Cursor typically use OAuth with the hosted MCP URL. ChatGPT uses OAuth for the custom app (OIDC off). API keys remain available on the setup page for clients that need them.
Can Perplexity join the same memory?
Yes, when connected to the same Palim account (Mac App currently uses an API key via mcp-remote). See the Perplexity integration docs.
Move one real decision across tools
Save something useful in ChatGPT, open Claude, and retrieve it before you continue.
Set up Palim