Memocore — one memory for Claude, Cursor and your whole team
Today ChatGPT is ahead, so you move to it. Then a new Claude model lands and you move back. Your memory, though, stays behind in the old tool. Everything you put into it — your stack, your conventions, a client's constraints, the decisions you agreed on — has to be dictated all over again.
It is the same story on a team. You and your colleagues work on the same things, but each of you has your own memory: what your Claude knows about the project, your colleague's ChatGPT does not.
Memocore is a memory layer that lives outside the AI client rather than inside it. A fact is saved once, and any tool you work with can read it — and add to it. So can your whole team, if you want them to.
One memory, any client
Memocore connects over MCP through a single address, memocore.ai/mcp. Cursor and VS Code connect in one click, ChatGPT from the plugin directory, Claude Code with one line in the terminal, Claude Desktop by pasting the address. Any client that supports MCP works.
For example: in the morning you work out in Claude why the project dropped Tailwind and ask it to remember that. In the evening a colleague opens Cursor, asks for a new component — and gets it without Tailwind. No need to explain it a second time.
There is also a Telegram bot: a note from a conversation goes straight into memory, and any memo can be sent back into any chat.
Personal notes
Private memos belong to you alone: preferences, personal facts, everything you are tired of repeating.
Projects sort that memory by topic: your work product in one, the apartment renovation in another, moving notes in a third, the series you have already watched in a fourth. Every project has a description of what goes into it, and your AI client uses that description to work out where new knowledge belongs — you do not have to say it every time. Tags let you filter, memo history shows who changed what and when, and files can be attached to a memo.
A personal project does not have to stay personal — you can share it with a family member, so the shopping list, the trip plans and the house paperwork stop living in one person's head. A single memo from a project can be shared with a link. And a project can carry instructions — rules every AI client must follow when writing into it, so even several people using different tools write memos the same way.
For teams
You can create a team and work in one memory with any number of people. Architecture decisions, code conventions, why a feature was dropped two quarters ago, how support handles a refund, onboarding a new hire — the knowledge a team normally re-explains in Slack every couple of weeks.
Need to give access to someone outside the team? A contractor, a client or a candidate often just needs to read part of the base, and paying a seat for them makes no sense. So a project can be opened read-only through a link — from the web or by connecting it to their own AI client — and such a reader takes no seat.
Your team's memory does not have to be read by hand. An API key exposes it — to support, to the chat on your site, to the help inside your own product. Through the key you can not only search but also write: a support bot files what the customer told it, an agent files what it learned during a run, and the next run starts with that already in place. The key is issued for selected projects, so only the part of the memory you opened goes out. The assistant answering questions about Memocore on our site works exactly that way.
Security
Memory is sensitive, so by default nothing leaves: until you open a memo or a project yourself, only you and the project's members can see it. Inside a company it is just as strict — a member of one project does not know another one exists until they are invited to it.
Sharing individual memos or whole projects comes with visibility settings: project, company, or fully public. Inside a project members have roles: an editor writes, a viewer only reads.
Every memo has a change history: you can see which member edited what, what they added and what they removed. Nothing changes silently.
We work on privacy and security constantly. Password encryption for a project is coming soon, for especially private data.
Start free
Free is not a trial: 100 memos, three projects, any MCP client, tags, history, public memo links and one public project. Paid plans lift the limits and add file uploads, and Team adds a shared company memory with roles, API keys and other integrations.
From the founder
Hi, my name is Andrei Gusev and I am the founder of Memocore.
Once I was dealing with a bureaucratic procedure: piles of numbers, addresses, dates and different documents. My AI agent kept mixing everything up and forgetting it from one chat to the next. So over a weekend I built Memocore — a small project, without even a web app, but it solved that big problem.
Memocore has changed beyond recognition since then, with a lot of new features, and we keep working on it every day. My AI agent now knows everything: the documentation for my projects, the decisions we made, even when my driver's licence expires and which films I have already seen, so it can suggest something new for the evening.
Thank you for reading this far. I hope Memocore turns out to be as useful to you as it is to me. I would be glad to hear any feedback — write to the chat bot, to [email protected], or to me on LinkedIn.