Skip to main content
Glama
Resume-State

ResumeState MCP Server

Official
by Resume-State
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ResumeState MCP Server

No user-submitted related servers found.

    Related Servers

    • CONTINUITY

      duke-of-beans
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides session persistence, crash recovery, decision tracking, and context compression for AI assistants, enabling seamless multi-session continuity.
      -

    • Amicus MCP Server

      earchibald
      F
      license
      B
      quality
      Not graded
      maintenance
      A state persistence layer that enables seamless handoffs between different AI coding assistants by maintaining a shared context bus. It provides tools for tracking summaries, next steps, and active files to ensure continuity across development sessions.
      3
      -

    • Soul

      choihyunsus
      F
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents persistent memory, handoffs, and shared context across sessions, enabling seamless continuity and multi-agent collaboration.
      23 npm
      67
      -

    • agent-work-mcp

      yurikaza
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to run persistent, budgeted work sessions with dependency graphs, human decision queues, required validation, and clean handoffs for autonomous or human-in-the-loop execution.
      16
      MIT

    • Worktrail

      jasonethicseo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to record and resume engineering work as durable, byte-exact threads of focus, decisions, evidence, and next steps.
      3
      Functional Source , Version 1.1, ALv2 Future
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct roles: replay_search/replay_get and list_artifacts/get_artifact are clean card-then-fetch pairs, and connect vs status are related but distinguishable. However, handoff, log_session, and ingest all read as 'record activity for this account,' and resume's fallback to listing lanes overlaps with list_lanes, creating some boundaries an agent could misjudge.

    Naming Consistency3/5

    A clear verb_noun convention exists in list_lanes, list_artifacts, get_artifact, and log_session, but replay_search/replay_get invert it to noun_verb while connect, resume, handoff, ingest, and status are bare verbs/nouns with no shared pattern. The mix is still readable in context but not predictable.

    Tool Count5/5

    Eleven tools is well within the ideal 3-15 range and each earns its place across connection, continuity, lanes, artifacts, replays, and ingestion. Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the continuity lifecycle well: connect/status for auth, resume/handoff for per-lane state, list_lanes for navigation, artifacts and replays for retrieval, and ingest/log_session for recording. Artifacts are read-only with no create/update/delete exposed, and lanes have no management operations, but these are plausible external responsibilities rather than dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources