Skip to main content
Glama

Related Servers

Alternatives to statecore-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local, cross-agent memory for AI coding agents using a single SQLite file, enabling persistent sessions and durable facts shared across multiple MCP-compatible tools.
      10 npm
      MIT
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      Persistent memory for AI coding agents, storing decisions, bug fixes, conventions, and discoveries in a local SQLite database and automatically recalling them when relevant. Works with Claude Code, Codex, Cursor, Gemini CLI, and other MCP-compatible agents.
      22
      2
      MIT
    • A
      license
      A
      quality
      A
      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
      14
      MIT
    • 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.
      -

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping role: remember writes durable facts, handoff captures session-ending state, recall retrieves relevant memory, facts enumerates beliefs, why traces provenance, and forget retires facts. No two tools could be easily confused even without deep inspection.

    Naming Consistency4/5

    Most tools use a single imperative verb (remember, handoff, recall, forget), which is consistent and predictable. However, 'facts' is a plural noun and 'why' is an interrogative, deviating slightly from the verb pattern; they remain intuitive in context.

    Tool Count5/5

    Six tools is a well-scoped set for a memory/state system. Each tool covers a distinct operation (write, session handoff, query, audit list, provenance, delete) without redundancy or bloat.

    Completeness5/5

    The surface covers the full memory lifecycle: storing facts, retrieving them, listing current beliefs, explaining provenance, handling session handoffs, and suppressing obsolete facts. There are no obvious missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues