Skip to main content
Glama
tianhuil

Agent State MCP Server

by tianhuil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Agent State MCP Server

No user-submitted related servers found.

    Related Servers

    • joa

      neethanwu
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent activity journal for AI agents - enables logging and querying decisions, changes, errors, and observations across sessions.
      7 npm
      1
      MIT

    • everrun

      UcelX
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides durable mission state for AI agents, enabling crash-safe recovery, verified completion, and explicit reconciliation of uncertain side effects without duplicate or blind retries.
      3
      Apache 2.0

    • agent-sessions

      mattmaas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to track session lifecycles, persist context notes and transcripts, and manage a human-gated memory-promotion pipeline with an append-only audit trail.
      1 npm
      MIT

    • worldmodel-mcp

      CocoaBeans
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides an external, validated state database for LLM agents to manage long-horizon tasks, with tools for defining schemas, invariants, actions, procedures, and branching, preventing state drift and compounding errors.
      -

    • AgentAudit MCP

      Rumblingb
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides an immutable, tamper-evident audit trail for AI agents, enabling event logging with cryptographic chaining, search, verification, and statistics.
      2
      MIT
    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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: load_log retrieves log data, load_state retrieves state data, log_message appends to the log, and update_state replaces state data. There is no overlap in functionality, and the resource-action pairs are unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent pattern: 'agent_state_' prefix followed by a verb_noun combination (e.g., load_log, update_state). This uniformity makes the tools predictable and easy to understand as a set.

    Tool Count5/5

    With 4 tools, this server is well-scoped for managing agent state and logs. Each tool serves a specific, necessary function (read/write for both state and log files), and there are no redundant or missing operations for this domain.

    Completeness5/5

    The tool set provides complete CRUD-like coverage for the domain: it supports reading and writing both state and log files. There are no gaps in functionality for managing agent persistence, and agents can perform all expected operations without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources