How can we help?

A memory your AI keeps between chats and clients. Your agent saves what matters as memos and recalls them later, so Claude, ChatGPT, Cursor and the rest all read and write the same memory instead of starting from nothing every time.

Open the connect instruction, copy your MCP endpoint and paste it into your client. Cursor and VS Code take one click; Claude, ChatGPT and the rest take a single line in their connector settings.

No. There is nothing to download — one endpoint is the whole setup.

Any client that speaks the Model Context Protocol — Claude, ChatGPT, Cursor, VS Code, Claude Code and others.

Ask your AI agent to remember it. Memos are created, edited and deleted by your agent over MCP; this site is where you read, search and organise them.

One thing worth remembering, written down by your agent: a fact, a decision, a recipe. It has a title, the text itself and a short preview, and it can carry tags and files.

A folder for memos on one topic. Each project has its own access, notifications and writing instructions, so a trip and a work account never mix.

They mark memos so both you and your agent find them faster. A tag can carry a short context line that tells the agent when to use it.

Yes. Ask your agent to save something for a few days and it is archived on its own once the time is up.

Yes, on any paid plan. Your agent uploads a file to the memo and can read it back later; the free plan is text only.

Every memo keeps its history — the Activity feed shows what was added, edited, archived or restored, and you can roll a memo back to an earlier version.

Nobody but you by default. A memo becomes visible to others only when you put it in a shared project or share it deliberately.

Turn sharing on for a memo in a project and you get a link. The link exposes only the title and the short preview — the full text stays with project members.

Projects anyone can follow. Their memos join the memory of everyone who follows them, so every AI client you connect knows what they know. Browse them in Explore.

A shared workspace for a team: its own projects, members and billing. Memory inside it belongs to the company, not to whoever wrote it, so people leaving or joining does not take it away.

Invite them by email from the company page, then add each person to the projects they actually need — nobody sees a project they were not invited into.

An editor reads and writes the memos of their projects; a viewer only reads them. Owners manage members, billing and integrations.

No. The company pays per active seat — $15 a month each — and that covers every member, their projects and the search behind them.

Yes. A company issues API keys, and each key is limited to the projects you tick for it, so your bot searches that memory and can write to it.

Yes. 100 memos, 3 projects and one public project, with no file uploads. Upgrade only when you outgrow it.

More memos and projects, file uploads and storage, and on Max a family member who shares your memory.

Unlimited memos and projects, 5 GB of storage per seat, API keys for your own products and external integrations — $15 per active seat per month.

Open Billing in the sidebar. Payments and cancellations go through Stripe, and your memos stay where they are either way.