ChatGPT's memory is OpenAI's. This one is yours.

ChatGPT remembers you — inside ChatGPT. The moment your workflow touches Claude, Cursor, or a coding agent, that memory is a silo: unexportable, uninspectable from outside, and gone from every other tool. Kognite connects to ChatGPT as a custom connector and stores memory in a graph you own, shared with everything else you run.

Vendor memory vs. portable memory

Built-in memory optimizes for the vendor's surface: what ChatGPT knows about you improves ChatGPT and nothing else. If you use one tool for everything, that trade is fine. Most people building with AI in 2026 don't — they chat in one product, code in another, and run agents in a third.

A memory server flips the ownership. Facts live in a store with an API, a dashboard, scopes, and an audit log; ChatGPT becomes one of several clients reading and writing it. Tell ChatGPT about your project tonight, and your Claude Code session has it tomorrow morning.

Add it as a connector

ChatGPT connects to remote MCP servers as Connectors (paid plans; you may need to enable Connectors or developer mode first). The server URL is the same for everyone: you sign in while adding it, and can revoke it later from the dashboard:

server URL
https://mcp.kognite.dev/mcp
  • Settings → Connectors → Add custom connector, paste the URL, then approve Kognite in the browser tab it opens. No secret in the URL, nothing to copy.
  • Enable the Kognite connector in a chat from the tools / Connectors menu.
  • Ask ChatGPT to “use the Kognite connector to remember / recall …” so it calls the tools rather than its own memory.

A memory with an inside you can see

  • Inspectable — every stored fact is visible, searchable, and deletable in the dashboard. No “what does it actually know about me?” mystery.
  • Structured — a knowledge graph with entities, relationships, and temporal edges, so recall can answer “who” and “when”, not just “something similar”.
  • Cross-vendor — the same store serves ChatGPT, Claude Desktop, Claude Code, Cursor, VS Code, Zed, Windsurf, and JetBrains AI. Eight documented setups, one URL each.
  • Yours to take — REST API and TypeScript/Python SDKs mean the memory outlives any one subscription.

Common questions

Does this replace ChatGPT's built-in memory?

It can coexist or replace it. For one authoritative cross-tool memory, rely on the connector and name it when asking to remember; the built-in memory keeps working independently if you leave it on.

Do I need a paid ChatGPT plan?

Custom connectors are a paid-plan ChatGPT feature. Kognite itself has a free tier — 5,000 new memories/mo with unmetered search.

Is the token-in-URL safe?

The URL both identifies and authenticates you, like a webhook URL. Treat it as a secret and rotate it from the dashboard in one click if it leaks.

What happens if I stop using ChatGPT?

Nothing — the memory lives in Kognite, not in ChatGPT. Every other connected tool keeps using it, and the REST API gives you programmatic access regardless.

Stop re-introducing yourself to every model.

One connector in ChatGPT, one URL in each coding tool — one memory across all of them. Free tier included.