Skip to main content
Glama
markmhendrickson

Neotoma

by markmhendrickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Neotoma

No user-submitted related servers found.

    Related Servers

    • nuzo-memory

      fabionfsc
      A
      license
      Not graded
      quality
      F
      maintenance
      Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
      2
      Apache 2.0

    • CP Memory

      CJhuochai
      A
      license
      C
      quality
      A
      maintenance
      Local-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.
      40
      25 PyPI
      1
      MIT

    • midas-memory-mcp

      vornicx
      A
      license
      A
      quality
      B
      maintenance
      Local-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.
      23
      50 PyPI
      14
      MIT

    • Mneme Memory MCP

      ethos-zero
      A
      license
      A
      quality
      B
      maintenance
      A local-first shared memory layer for MCP-aware agents like Claude, Codex, and Hermes, enabling persistent memory across chats and clients via Markdown files and SQLite FTS.
      6
      2
      MIT

    • 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.
      -
    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

    C2.8/5.0

    Scored across 63 tools

    Disambiguation3/5

    Several clusters have blurry boundaries: retrieve_entities vs retrieve_entity_by_identifier vs identify_entity_by_signals vs retrieve_entity_snapshot all serve entity retrieval/resolution, and list_relationships vs retrieve_related_entities vs retrieve_graph_neighborhood overlap in what they return. Individual descriptions help (e.g., identify_entity_by_signals is clearly signal-based), but an agent faces genuine selection risk across these groups.

    Naming Consistency3/5

    The dominant verb_noun snake_case pattern (retrieve_X, list_X, create_X, delete_X, sync_peer) is mostly consistent, but there are notable breaks: bare single-verb tools (store, correct, subscribe, unsubscribe) sit alongside compound forms, and the same action uses inconsistent prefixes (retrieve_entities vs get_entity_submission_status vs list_entity_submissions). npm_check_update and neotoma_turn_summary break the convention entirely.

    Tool Count2/5

    At 63 tools this is well into the heavy range, and many tools feel like surface-area inflation beyond core domain work: npm_check_update, neotoma_turn_summary, health_check_snapshots, get_session_identity, and describe_instance_policy are auxiliary/observability concerns that dilute the tool surface. Even accounting for the large knowledge-graph + sync scope, the count is excessive.

    Completeness4/5

    The domain surface is unusually comprehensive: full entity lifecycle (store, retrieve, delete, restore, merge, split), relationship lifecycle (create, list, delete, restore, traverse), schema management (register, describe, update), issues (submit, status, sync), and subscriptions/peers all have complete CRUD coverage. The main gap is resolve_sync_conflict being a stub, but the rest of the surface leaves few dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources