Claude, ChatGPT, Cursor and your other AI tools save to it as they work and read from it when they start. You and your team read the same memory, ask it questions and add files, so nobody has to explain the same thing twice.
The problem
Claude Code forgets what you decided yesterday. Cursor does not know what ChatGPT learned this morning. You explain the same project and the same rules again in every tool, every session. And what one person’s AI learns stays in that person’s chat history, where the rest of the team can’t see it.
Context Engine is the memory your AI tools and your team share. It is a hosted service at app.contextengine.com that you sign in to with your email. You connect your AI tools once, and as they work they save what matters into it: decisions, notes, people, customers and files. The next session starts with all of that, and anyone on your team can read it.
How it works
Pick the app you use. ChatGPT and Claude take a few clicks, and Claude Code takes one command. Each connection reaches only the engines you choose, and there is no key to copy or keep safe.
Saves to Invoicing app
$ claude mcp add --scope user --transport http ce-invoicing \ https://app.contextengine.com/mcp/c/k7f2q9
As you work, your AI tools save what matters: a decision, a customer’s request, a new contact. Each memory has a type, shows which tool saved it and keeps its history. You can also drop in files, a whole folder or a .zip.
When a tool starts, it gets a short brief: what each engine is for, what happened recently and what changed since its last visit. If it needs more, it searches the memory, matching meaning as well as exact words. You read the same memory in the app, so you can always see what your tools know.
Brief
Invoicing app: code, customers and decisions for our invoicing product.
Since you were last here
Engines
Say in a sentence or two what an engine is for. Your AI tools read that purpose to decide what to save where, so the client’s decisions land in the client’s engine and your own notes stay yours.
Keeps itself in order
Context Engine writes summaries, links related memories and catches duplicates, so what was saved last month is still useful this month, to your team and to your tools.
Ask in plain words. Every answer names the memories it came from.
Card payments retry at most three times, down from five after August’s disputes. A card flagged as stolen or fraudulent is never retried.
A short account of each day, rolled into weeks and months, from what was saved.
Card retries took the day: after August’s disputes the team cut retries from five to three, and Jon drafted the runbook change. Contoso asked for invoices grouped by cost centre.
People, customers, decisions and files connect to each other, and the map shows how.
When a tool tries to save something already there under the same name, it is pointed to that memory to update instead.
Every change records who made it, with which tool, and what it was before.
Works with
Sign in from the apps below, or connect anything that speaks MCP or HTTP with a key.
Made for how you work
If you build with AI
The decision you made with Claude Code on Monday is known to Cursor on Tuesday. You stop re-explaining your conventions, your stack and why you chose it.
If you work for several clients
Give each client an engine and a connection of its own. In Claude Code, a project-scoped connection keeps each client’s repository to that client’s memory.
If you work as a team
Invite your whole team on any plan, at no cost per person, as owner, admin, member or viewer. Everyone reads the same memories and gets the same answers, whichever tool they use. See every tool that reaches the engine, and cut one off in a click. When someone leaves, what they saved stays in the engine, still credited to them.
Security and privacy
Your memory belongs to you and is stored apart from every other customer’s. You can see all of it, and take it with you.
Export an engine any time as one ZIP of Markdown and JSON that opens without us. Every memory is a plain Markdown file.
Every engine gets its own database, its own search index and its own running copy of the service. It never shares a table with anyone else’s data.
Your content is sent to models only to answer you. It is not used to train anything, not sold and not used for advertising.
Support opens an engine only when you approve a request, for the time it names, and every visit is logged. A legal or safety duty is the one exception, and you are told at once.
See every tool and key that can reach an engine, with its access and when it was last used. Pause it, or cut it off.
Deleting an engine is scheduled a day ahead so you can export first. Then it is gone. Choose the EU at setup to keep its database and files there.
Two-step sign-in is built in, and Enterprise adds single sign-on through OpenID Connect (Okta, Entra ID, Google). Read the privacy notice.
No, and it does not run your agents. Your AI tools do the thinking. Context Engine is the memory they share: they save to it as they work and read from it when they start. You can also ask it questions yourself, and every answer names the memories it came from.
Both. Your AI tools save to it as they work and read from it when a session starts. People use the same memory in the app: browse every memory and who saved it, ask questions and get answers that name their sources, read summaries of each day and week, and drop in files. Your whole team shares it on every plan, at no cost per person.
ChatGPT, Claude on the web and the desktop app, Claude Code and Cursor sign in with a few clicks. Anything else that speaks MCP or HTTP connects with a key, so agents and scripts you build yourself can use the same memory.
An engine is a memory with a purpose: a few sentences, in your words, saying what it is for and what belongs in it. Your AI tools read the purpose to decide what to save there. Keep one for yourself, one per client or project, or one for a team.
Yes. Each engine is stored on its own, and each connection reaches only the engines you tick, at Can read or Can read and save. Give each client its own engine and its own connection, and nothing crosses between them.
Every engine gets its own database, its own search index and its own running copy of the service, on Cloudflare. Your content is sent to models only to answer you and is never used to train anything. Context Engine support opens an engine only when you approve a request, for the time it names, and every visit is logged.
Any time. Export gives you one ZIP of Markdown and JSON that opens without us: every memory is a Markdown file, so a text editor or a notes app reads it as it is. Deleting an engine is scheduled a day ahead so you can export first, and then it is gone.
Every plan lets your AI tools read and save as much as they need; what an engine’s plan sets is how many agents connect to it and how much memory it holds. You are told before your memory is full. When it is, a new memory is refused with the reason, and nothing you stored is ever deleted.
Relote built it and runs it. If you want help putting AI to work across your company, that is Relote’s work, at relote.com. Context Engine itself is the product: sign up, connect your tools, and it works.