Skip to main content
Glama
sovantica

engrava-mcp

by sovantica

Related Servers

Alternatives to engrava-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a drop-in MCP memory server over stdio using a local SQLite store, enabling agents to store, search, and audit memory with provenance, scoped access, and contradiction tracking without requiring API keys, LLMs, or embedding providers.
      318 npm
      16
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables any MCP-compatible agent to query a local OpenRhyme activity timeline, search history, and issue control commands over stdio while keeping all data on-machine.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes the mindgap knowledge graph as an MCP server over stdio, providing tools to add, link, query, and manage nodes and edges in a local org-roam-style graph.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Serves UltraRAG memory to agents over stdio MCP, providing project-local and per-user global memory. It lets agents read and append standing memory and daily dialogue rounds in UltraRAG's format, with an optional browser view.
      4
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to persist, recall, update, forget, and search agent memories over stdio, backed by Postgres with pgvector for vector search. Supports cross-session memory validation with per-operation latency and outcome logging.
      1
      -

    TDQS

    A3.8/5.0

    Scored across 13 tools

    Disambiguation4/5

    The four read paths (search_memory, search_keywords, list_memory, query_memory) overlap conceptually, but each description explicitly contrasts itself with the others (ranked vs. unranked, hybrid vs. BM25, structured MindQL) so an agent can pick correctly. Similarly, get_edges (edges touching one thought) vs. list_edges (global filtered edge browse) is distinguishable but confusable on first read.

    Naming Consistency3/5

    Most names follow verb_noun, but conventions drift across entities: thoughts use store/get/update/delete_thought while edges use link_thoughts plus delete_edge, and memory_stats is the one noun-only name. The entity vocabulary also shifts between 'thought' and 'memory' (store_thought vs list_memory/search_memory), which muddies the pattern.

    Tool Count5/5

    13 tools sit comfortably in the well-scoped range for a memory-graph server, with reads, writes, deletes, and analytics each represented. No tool looks like filler or a near-duplicate of another.

    Completeness4/5

    Thoughts have full create/read/update/delete plus ranked, keyword, structured, and paged listing, and edges have create/read/delete; deletion cascades are documented. The notable gap is that edges have no update operation, so weight or metadata on an existing edge cannot be changed without deleting and re-linking it.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues