Mmcp.market

hmem — Humanlike Memory for AI Agents MCP server

by Bumblebiber·io.github.Bumblebiber/hmem-mcp·v1.6.7·24 stars

Persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

24 stars132 downloads/wk

Reviews

Write one

Nobody has reviewed hmem — Humanlike Memory for AI Agents yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

hmem — Humanlike Memory for AI Agents tools (11, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • append_agent_memory

    CURATOR ONLY (ceo role). Append new child nodes to an existing entry in any agent's memory.

  • append_memory

    Append new child nodes to an existing memory entry or node (your own personal memory).

  • delete_agent_memorywrite action

    CURATOR ONLY (ceo role). Delete an entry from any agent's memory.

  • fix_agent_memory

    CURATOR ONLY (ceo role). Correct a specific entry or node in any agent's memory.

  • get_audit_queue

    CURATOR ONLY (ceo role). Returns agents whose .hmem has changed since last audit.

  • mark_audited

    CURATOR ONLY (ceo role). Mark an agent as audited (updates timestamp in audit_state.json).

  • read_agent_memory

    CURATOR ONLY (ceo role). Read the full memory of any agent (for audit purposes).

  • read_memory

    Read from your hierarchical long-term memory (.hmem).

  • search_memory

    Searches the collective memory: agent memories (lessons learned, evaluations),

  • update_memorywrite action

    Update the text of an existing memory entry or sub-node (your own personal memory).

  • write_memorywrite action

    Write a new memory entry to your hierarchical long-term memory (.hmem).

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan19 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 69 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install hmem — Humanlike Memory for AI Agents in Claude Code, Cursor or VS Code

Runs npx -y hmem-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add hmem-mcp -- npx -y hmem-mcp
Add to Cursor

What the publisher says

From the hmem — Humanlike Memory for AI Agents repository's README, as published. We do not edit it. Read it on GitHub

hmem — Humanlike Memory for AI Agents

Your AI forgets everything between sessions. hmem fixes that.

One loadproject() call. ~3000 tokens. Your agent knows everything important about a project — every past mistake, every decision, every open task — across sessions, devices, and AI providers. No setup per conversation. No "let me re-read the codebase." It just remembers*.

AI agent? Skip this file. Read AGENT_SETUP.md — written for you, not for humans.

Naming note (v8.0): This package was briefly published as its-over-9k (1.x). It is now hmem again — pure memory framework, nothing else. The its-over-9k name lives on as a separate project: the o9k token-efficiency meta-framework, which combines skills/plugins like this one. Related: TIM — hmem's next-generation successor (hypergraph memory, CRDT sync).

What This Is

hmem is not a note-taking plugin. It's a memory framework for AI agents — a complete infrastructure layer for persistent, portable, token-efficient knowledge that survives session boundaries, device switches, and provider changes.

Four core guarantees:

The Problem

Every AI session starts from zero. Your agent asks the same questions, makes the same mistakes, contradicts last week's decisions, and wastes 50k tokens loading context it already processed yesterday.

You've tried workarounds — CLAUDE.md files, custom prompts, manually pasting context. They don't scale. You have 10 projects. You switch between 3 devices. You use different AI tools.

The Solution

You:    "Load project"
Agent:  [calls load_project("P0048") — 3000 tokens]
Agent:  "v1.2.9, TypeScript/SQLite/npm. 3 open bugs, 8 roadmap items.
         Last session: rebrand complete, rename_id bug fixed (89 changes).
         Next: O-Entry Auto-Purge. What's the focus today?"

That's it. 3000 tokens for a complete project briefing. The agent knows the stack, the architecture, the open bugs, the recent decisions, and exactly where you left off — even if "you" was a different AI on a different machine yesterday.

How It Works

Level 1  ──  One-line summary          (always loaded — ~5k tokens for 300+ entries)
  Level 2  ──  Paragraph detail        (loaded on demand)
     Level 3  ──  Full context          (loaded on demand)
      Level 4  ──  Extended detail      (loaded on demand)
        Level 5  ──  Raw/verbatim data  (loaded on demand)

At session start, the agent loads Level 1 summaries — one line per memory. When it needs detail, it drills down. Your 300-entry memory costs 5k tokens to overview. A single project costs ~3000 tokens.

Nothing is summarized away. Level 1 is a compressed view, but Levels 2–5 hold the complete original text, word for word, accessible on demand.

Framework Features

Automatic Session Memory

Every conversation is recorded automatically. No "save your work" prompts. No manual checkpoints.

You type  →  Agent responds  →  Stop hook fires  →  Exchange saved to O-entry
                                                   →  Linked to active project
                                                   →  Haiku auto-titles the session

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

hmem — Humanlike Memory for AI Agents: common questions

Is hmem — Humanlike Memory for AI Agents MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the hmem — Humanlike Memory for AI Agents safety report
How do I install hmem — Humanlike Memory for AI Agents?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does hmem — Humanlike Memory for AI Agents need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is hmem — Humanlike Memory for AI Agents maintained?
The last commit was 69 days ago (2026-07-21). The latest release is v1.6.7.
What can I use instead of hmem — Humanlike Memory for AI Agents?
Servers from other publishers that do the same job: SAME - Stateless Agent Memory Engine MCP server, LoreConvo MCP server and Local Memory MCP server. Compare all hmem — Humanlike Memory for AI Agents alternatives.

Alternatives to hmem — Humanlike Memory for AI Agents

Same job from other publishers: the closest match first, then the best rated.

All hmem — Humanlike Memory for AI Agents alternatives →
  • SAME - Stateless Agent Memory Engine
    Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.
    B
  • LoreConvo
    Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.
    B
  • Local Memory
    Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys.
    A
  • Amnesic
    Persistent semantic memory for SQL databases. Postgres, MySQL, MSSQL, SQLite.
    A
  • Engram
    Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
    A

More from Bumblebiber →