Hippo Memory MCP Server: Setup for Claude Code, Cursor and Other Apps

• Searches your saved project memories for a topic

  Finds the memories that match a question and returns them ranked by relevance, strength and recency, within a size limit you can set. It can also add the active task notes and the last session handoff, which helps at the start of a session.

  Try: “Recall what we learned about the payment webhook retries.”

  Read · hippo_recall

• Builds an ordered context window for one session

  Takes a session ID and returns that session's recent messages untouched, plus short summaries standing in for older ones, trimmed to a token budget. It drops the weakest items first, not the oldest.

  Try: “Assemble the context for session abc123 within 4,000 tokens.”

  Read · hippo_assemble

• Opens a summary to see the memories behind it

  When a recalled item is a summary, this returns the original memories it replaced, one level down or more. Use it to recover the detail a summary left out.

  Try: “Show me the original notes behind that summary.”

  Read · hippo_drill

• Saves a new memory

  Stores a short fact for later sessions. You can mark it as an error, which keeps it twice as long, pin it so it never fades, or tag it. Unpinned memories fade unless they are recalled.

  Try: “Remember that the staging database needs the VPN on.”

  Write · hippo_remember

• Says whether the last recalled memories helped

  Records if the memories you just got were useful. Good ratings slow a memory's fade and bad ones speed it up.

  Try: “Mark those memories as helpful.”

  Write · hippo_outcome

• Loads memories for what you are working on now

  Reads the current git state to guess the task, then returns matching memories with the active task notes, the session handoff and the recent session trail. Memories from private sources are left out unless you ask for that scope.

  Try: “Load the context for this branch.”

  Runs code · hippo_context

• Shows the health of the memory store

  Returns counts, memory strengths, memories at risk of fading and the time of the last consolidation.

  Try: “How healthy is the memory store?”

  Read · hippo_status

• Turns recent git fixes and reverts into memories

  Scans recent commits for fix, revert, bug, refactor and perf patterns and saves lessons from them. You choose how many days back to scan, and it skips duplicates.

  Try: “Learn from the last 14 days of commits.”

  Runs code · hippo_learn

• Lists memories that contradict each other

  Returns the open conflicts, which are pairs of memories that disagree and need a decision.

  Try: “Are there any conflicting memories?”

  Read · hippo_conflicts

• Settles a conflict by keeping one memory

  Keeps one memory from a conflict and weakens the other. With the forget option it deletes the loser, and with the reject option it also blocks that value from coming back.

  Try: “Resolve conflict 7 and keep memory m_42.”

  Delete · hippo_resolve

• Copies a memory to the global store

  Shares one memory so other projects on this machine can use it. It scores how well the memory transfers and refuses low scores unless you force it.

  Try: “Share memory m_42 with my other projects.”

  Write · hippo_share

• Lists projects that added to the global store

  Returns every project that has contributed memories to the shared global store.

  Try: “Which projects share memories here?”

  Read · hippo_peers

• Checks how past estimates compared with reality

  Takes a cohort label such as migration-effort and returns how closed predictions in that class turned out: counts, average estimate against actual, ratios and a summary. Use it to sanity-check a new estimate.

  Try: “What is our track record on migration-effort estimates?”

  Read · hippo_predict_baserate

Watch out for

• hippo_resolve can delete memories

  With the forget option it deletes the losing memory, and with the reject option it also blocks that value from returning. Ask the assistant to confirm before it resolves conflicts. github.com

• hippo_learn reads your git history

  It scans recent commits and saves lessons from them as memories. Commit messages end up in the memory store and can be recalled in other projects if shared. github.com

• Shared store crosses projects

  hippo_share copies a memory to a global store that other projects can read. Do not share memories that hold client or secret details. github.com

• Memories fade unless recalled

  Unpinned memories decay over time, so a fact the assistant saved can drop out of results later. Pin the ones that must stay. github.com

• hippo init adds hooks and a daily job

  Running hippo init writes hooks into your agents' settings and sets up a daily 6:15am run. With ANTHROPIC_API_KEY set, the sleep step that runs at session end sends memory text to Anthropic; the README says an extraction setting in .hippo/config.json turns that off. github.com

Security advisories