Skip to main content
Glama
Koolercat

Decision State MCP

by Koolercat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Decision State MCP

No user-submitted related servers found.

    Related Servers

    • graphify

      Ibrohim-Bxone
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code that stores decisions and summaries locally, enabling Claude to recall past context across chats.
      1
      MIT

    • Cortex

      ProductionLineHQ
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.
      1,117 npm
      1
      MIT

    • recall

      Zavelinski
      A
      license
      A
      quality
      D
      maintenance
      A zero-dependency MCP server for cross-session memory recall in Claude Code. Provides lexical search, listing, and retrieval of past session memories to avoid re-explaining context.
      3
      12 npm
      MIT

    • threadline-core

      richardoros
      A
      license
      A
      quality
      B
      maintenance
      MCP server providing structured continuity memory for AI coding agents, tracking decisions, open loops, and session state in local SQLite. Enables agents to resume work from verified state across sessions without replaying transcripts.
      17
      Apache 2.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation or entity: session, state, task context, decision, evidence, outcome, search, and state update. No two tools have overlapping purposes, ensuring clear differentiation for an agent.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with 'get_' for retrieval and 'record_' for persistence, but 'reflect_outcome' deviates from the 'record_' convention. Overall, the naming is predictable and readable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a decision state management server. Each tool serves a clear purpose without excess or deficiency.

    Completeness4/5

    The tools cover the core lifecycle: reading state, adding decisions/evidence/outcomes, searching, and updating. Minor gaps exist (e.g., no explicit get_decision or update/delete for decisions), but the surface is largely complete for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources