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
      31 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      13 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
      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
      17 PyPI
      15
      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.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct memory lifecycle stage: remember creates, recall/facts read (query vs full audit), forget retires, why explains provenance, and handoff manages session continuity. The only mild ambiguity is facts vs recall, but their descriptions clearly differentiate full audit from query-budgeted retrieval.

    Naming Consistency4/5

    All tool names are lowercase single words and mostly imperative verbs (remember, recall, forget, handoff), so the style is consistent and readable. 'facts' and 'why' are noun/question-word deviations rather than verb forms, but they are not mixed conventions.

    Tool Count5/5

    Six tools is well-scoped for a project-memory server: storage, retrieval, audit, forgetting, provenance, and session handoff each get one slot without redundancy. The count feels neither thin nor heavy.

    Completeness4/5

    The core memory lifecycle is covered: create (remember), read (recall/facts), delete (forget), provenance (why), and session handoff. The main gap is no explicit fact-update tool, though supersession/versioning is hinted at and forget+remember provides a workaround.

    Maintenance

    ActivityActive
    ResponsivenessNo issues