Hippo Memory — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track memory persistence and agent-harness integrations as the project evolves

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Local long-term coding-agent memory that learns from outcomes

What we know

Local SQLite memory for coding agents with recall, remember and outcome feedback, designed to share memory across Cursor, Claude Code and Codex.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)feat: run the memory quality repair once after an upgrade ( 500)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Local memory database access. Writes: Store/update memory state.
Authentication not yet verified.
Sensitive access: Project context, Developer history

Local-only storage is a strong boundary, but durable memory still needs filesystem protection and backup policy.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

757 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Which coding-agent memory operations does Hippo currently expose?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Local-only storage is a strong boundary, but durable memory still needs filesystem protection and backup policy.
Local memory database access.
Project states memory stays in SQLite on the user's machine and needs no account/model.
Reviewed write actions: Store/update memory state
Sensitive access: Project context, Developer history
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Persistent memory can accumulate sensitive engineering context.
Retention/backup policy depends on the local deployment.

Original activity observations

2026-10-05T14:56:56Z: feat: run the memory quality repair once after an upgrade ( 500)

Technical identity

github.com/kitfunso/hippo-memory

Exact implementation source: https://github.com/kitfunso/hippo-memory ↗
Reviewed resource type: MCP Server
Repository identity: kitfunso/hippo-memory

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
kitfunso/hippo-memory
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

claude-desktop

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher: Node.js >=22.16; `npm install -g hippo-memory && hippo init` inside a project. `hippo init` also installs hooks / instruction blocks and can add a daily task; npm installation alone does not enable agents.
package install · Publisher instructions
npm install -g hippo-memory
self hosted install or run · Publisher instructions
hippo init
Configure / authenticate
MCP100 setup guide
Install npm install -g hippo-memory, then hippo init in the intended project. Init installs agent hooks and can schedule automatic work; read side effects first. Optional Anthropic extraction can transmit memory content.
Advanced configuration · claude desktop json · MCP100 composed guide
claude desktop json · MCP100 composed guide
{ "mcpServers": { "hippo-memory": { "args": [ "mcp" ], "command": "hippo" } } }
Check connection
Publisher instructions
Run publisher `hippo doctor` after `hippo init`; verify the intended agent integration, not just the npm package binary.
read only local inspection · Publisher instructions
hippo doctor
Remove / uninstall / revoke
MCP100 setup guide
First remove installed hooks and daily schedule/config introduced by `hippo init` according to the local project/agent configuration; unregister `hippo-memory` MCP separately. Preserve .hippo data.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
npm uninstall -g hippo-memory

Official Documentation & Sources

What it does

Local SQLite memory for coding agents with recall, remember and outcome feedback, designed to share memory across Cursor, Claude Code and Codex.

Capability: Files & Knowledge
Resource type: MCP Server
Industry: Software & Technology
Best fit: Local long-term coding-agent memory that learns from outcomes

Representative uses

Recall prior project memory
Store lessons/decisions
Mark recalled memory good/bad
Share memory across coding agents

Limitations

Persistent memory can accumulate sensitive engineering context.
Retention/backup policy depends on the local deployment.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Local memory database access.
Data handling: Project states memory stays in SQLite on the user's machine and needs no account/model.
Cost: free
Risk and cautions: Local-only storage is a strong boundary, but durable memory still needs filesystem protection and backup policy.

Access scope and cautions

Write actions: Store/update memory state
Sensitive access: Project context Developer history
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Recall prior project memory; Store lessons/decisions; Mark recalled memory good/bad; Share memory across coding agents.

What setup information is documented?

Recorded installation/entrypoint step: claude mcp add hippo-memory -- hippo mcp. Recorded transport: stdio. Prerequisites: Hippo installed locally. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Documented write actions include: Store/update memory state. Recorded permission boundary: Local memory database access.

What data-handling boundary should I consider?

Project states memory stays in SQLite on the user's machine and needs no account/model. Recorded sensitive-access context: Project context; Developer history.

What limitations and risks should I check before use?

Local-only storage is a strong boundary, but durable memory still needs filesystem protection and backup policy. Persistent memory can accumulate sensitive engineering context. Retention/backup policy depends on the local deployment. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

kitfunso is listed as Community implementation in MCP100’s current evidence.