Skip to main content
Your AI assistant forgets everything when the session ends. The EverOS MCP server (everos-mcp) plugs EverOS memory into any MCP client, so the assistant remembers what you told it, builds a profile of how you work, and learns from how past tasks were solved, on every machine you use.
Building your own app? Call EverOS from code with the Python SDK instead. This page is for adding memory to an AI tool you already use.

What your assistant can do

  • Remember across sessions. Facts, decisions and preferences you mention are stored and recalled when they are relevant, not pasted into every prompt.
  • Know who you are. EverOS builds a profile from your conversations, and the assistant loads it at the start of each session.
  • Learn from experience. How a task was solved, tool calls included, is distilled into cases and skills the assistant recalls the next time a similar task comes up (local server only).
  • Use memory when it helps. The server describes when to load the profile, store new facts and recall context, so capable assistants do it without a prompt from you. Ask it not to remember something and it won’t.
  • Keep secrets out. Writes that contain API keys, tokens, private keys or passwords are refused, and recalled memories are treated as data, never as instructions.

Choose how to connect

Connect Claude or ChatGPT

The connector runs on EverOS Cloud at https://everos-mcp.evermind.ai/mcp. You sign in with your EverOS account and choose which memory space the app can use. No API key is involved.
1

Add the connector

In Claude, open Settings → Connectors, choose Add custom connector, and enter:
The connector then works in Claude on the web, desktop and mobile.
2

Sign in and choose a space

Your browser opens the EverOS consent page. Sign in, check the app and the address it returns to, pick the memory space it may read and write (or create a new one), and choose Allow.
3

Try it

Tell the assistant something worth remembering, start a new chat, and ask about it.

Manage connected apps

Every app you connect is listed under Connected Apps in the EverOS Console, with its memory space and when it was last used.
  • Revoke disconnects the app at once. Its stored memories stay in the space.
  • Reconnect with a different space disconnects the app; reconnect from the app and pick the new space on the consent page.
  • A connection that goes unused for 30 days is disconnected automatically. Connect again from the app to continue.

Run the server locally

1

Get an API key

Create one in the EverOS Console.
2

Install uv

The server runs with uvx, so there is nothing else to install. If you don’t have uv yet:
3

Add the server to your client

4

Try it

Tell your assistant something worth remembering, start a new session, and ask about it.

Tools

Read-only tools are marked as such, so clients can run them without a permission prompt. forget_session is marked destructive.
The profile, cases and skills are built in the background and appear seconds to minutes after a write. A memory saved with wait=true can also take a moment to show up in search, because the index catches up after extraction finishes. A trajectory needs more than three tool-call rounds to become a case; shorter ones are still stored as memories.

Your data

  • What is stored: the facts and exchanges the assistant saves with add_memory, and the profile EverOS builds from them. The local server also stores the task trajectories it records. Beyond that, EverOS receives only what a tool call carries, such as the query for a search.
  • Where: in your EverOS account, in the memory space you chose (connector) or the space of your API key (local server).
  • Removing it: ask the assistant to forget the current conversation (forget_session), or delete the whole memory space under Memory Spaces in the EverOS Console. Revoking a connected app stops its access but keeps what it stored.
See the Privacy Policy and Terms of Service.

Configuration (local server)

Set these as environment variables in the client config, next to EVEROS_API_KEY.

Self-hosted EverOS

Point the server at your own EverOS deployment. No API key is needed for a host that is not on evermind.ai.

Learn more

everos-mcp on GitHub

Source, security policy, and running it as a shared HTTP server for a team.

Memory lifecycle

How EverOS turns conversations into episodes, profiles, cases and skills.