Skip to main content
Glama
stoneskin

open-memex

by stoneskin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to open-memex

  • Remnic

    joshuaswarren
    A
    license
    Not graded
    quality
    A
    maintenance
    Local-first memory for AI agents: one store shared by Claude Code, Codex CLI, Cursor, Pi, Hermes, OpenClaw, and any MCP client. Plain markdown with YAML frontmatter on your disk, hybrid BM25 + vector recall with per-result provenance (Recall X-ray), a correction contract, and the MemCorrect benchmark.
    213
    MIT

Related Servers

  • auxly-memory-cli

    Tzamun-Arabia-IT-Co
    A
    license
    Not graded
    quality
    A
    maintenance
    Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
    2
    MIT
  • Memryzed by memryzed

    Memryzedofficial

    memryzed
    F
    license
    Not graded
    quality
    C
    maintenance
    Local-first cross-agent memory for AI coding agents. Persistent, shared memory over MCP — what you tell one agent can be recalled by another — with all data stored in a single local SQLite file, no cloud and no API keys.
    -

  • peon-mem

    VineetV2
    A
    license
    Not graded
    quality
    A
    maintenance
    Local-first hierarchical memory for AI coding agents, providing automatic session capture, belief consolidation, and relevant memory injection via an MCP server.
    112 npm
    2
    MIT

  • memmd-mcp

    matamong
    A
    license
    B
    quality
    D
    maintenance
    A shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client.
    4
    2
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 11 tools

Disambiguation4/5

Core operations (add, search, list, supersede, forget) are clearly distinct. The workflow-stage tools (promote, submit, propose) and the two status tools (status, pr_status) have adjacent purposes, but descriptions differentiate them well enough that misselection is unlikely.

Naming Consistency5/5

Every tool uses a consistent memory_ prefix with snake_case verb or verb_noun naming (memory_add, memory_search, memory_pr_status, memory_supersede). The pattern is predictable and uniform throughout.

Tool Count5/5

11 tools is well within a comfortable range and each maps to a distinct action in a memory lifecycle (CRUD, search, review promotion, git sync). No tool feels redundant or filler.

Completeness4/5

The surface covers the full memory lifecycle: create, search, list, supersede, forget, review-ladder promotion, git conflict resolution, and outbox-to-repo sync. Minor gaps exist (e.g., no explicit memory_update/edit or bulk operations) but core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources