Skip to content

MCP memory server for Claude Code, Cursor and Windsurf

hippo mcp runs a memory server over stdio on your machine, with no account and no API key. Any MCP client can use it, including Claude Code, Cursor, Windsurf (now Devin Desktop), Cline and Claude Desktop. The agent gets 13 tools to recall and store memories, mark what it recalled as helpful or wrong, and see where memories contradict each other.

Add it to your client

$ claude mcp add hippo-memory -- hippo mcp

That is all Claude Code needs. Other clients take a config block. Cursor reads it from .cursor/mcp.json, Claude Desktop from claude_desktop_config.json, and Windsurf and Cline from their own MCP settings.

{
  "mcpServers": {
    "hippo-memory": {
      "command": "hippo",
      "args": ["mcp"]
    }
  }
}

With no global install, "command": "npx", "args": ["-y", "hippo-memory", "mcp"] works too. If there is no store yet, the first tool call creates the global one in ~/.hippo. The server gives an agent tools and captures nothing by itself, so run hippo init as well for the agents that support hooks.

The 13 tools

Tools the hippo MCP server exposes
Tool What it does
hippo_recall Memories that match a query, ranked within a token budget.
hippo_assemble A session's context in time order, within a token budget.
hippo_drill Opens a topic summary and lists the memories under it.
hippo_remember Stores a memory. Errors get twice the half-life, and pinned memories never decay.
hippo_outcome Reports whether the recalled memories helped.
hippo_context Works out the current task from git and returns matching memories.
hippo_status Counts, strengths and when the store last slept.
hippo_learn Scans recent git commits and stores the lessons.
hippo_conflicts Lists memories that contradict each other.
hippo_resolve Settles a conflict by keeping one memory.
hippo_share Copies a memory to the global store for other projects.
hippo_peers Lists the projects that feed the global store.
hippo_predict_baserate Base rates for past predictions, to check a new one against.

Where the memories live

The question to ask of any MCP memory server is where the memories live and who runs it. The servers from Mem0, Zep and Letta are hosted and need an account or an API key. In mem0's words (opens in new tab), memories stored that way "live in your Mem0 account, not on your computer". Hippo keeps them on your machine. It also adds the ability to mark a recalled memory wrong, replace an old fact and list contradictions.

hippo vs mem0, hippo vs Zep, hippo vs Letta

MCP questions

All 14 questions

Can I use hippo as an MCP memory server?

Yes. hippo mcp runs the server over stdio. Add it to the MCP config of Cursor, Claude Desktop, Windsurf (now Devin Desktop), Cline or any other client, or in Claude Code run claude mcp add hippo-memory -- hippo mcp.