F
licenseA
qualityB
maintenanceAn agent-native workflow MCP server that enables AI agents to execute text-defined, versionable workflows with checkpointing and state management.
10
7 npm
-
MCP State Sidecar Server
by askadvaith
Related Servers
Alternatives to MCP State Sidecar Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables durable handoffs and shared scratchpad for multi-agent workflows over MCP HTTP transport.29 npmMIT
- AlicenseAqualityAmaintenancePersistent, branch-aware workflow state memory MCP server for AI coding assistants. Tracks tasks, accepted decisions, and active blockers to prevent session context bloat and speed up development.137,375 npm82MIT
- AlicenseNot gradedqualityAmaintenanceDurable, user-keyed state management for stateless MCP servers. Enables agents to persist and resume state across conversations, clients, and devices.MIT
- AlicenseAqualityBmaintenanceShared versioned state for multi-agent AI workflows. An MCP server.589 PyPI2MIT
- AlicenseAqualityAmaintenanceGoverned agent execution gateway for LLM workflows, providing deterministic FSM-based execution, audit trails, and idempotency guarantees via MCP.5MIT
TDQS
A3.9/5.0
Scored across 19 tools
Disambiguation5/5
Each tool targets a distinct resource (history, leases, sessions, sidecar admin, state store, workflows) with clear boundaries. Even overlapping descriptions like workflow_list and workflow_discover are differentiated by purpose—list shows all, discover filters by tags/status—ensuring no ambiguity.
Naming Consistency5/5
All tools consistently use snake_case with a noun_verb pattern (e.g., lease_acquire, state_get, workflow_create). Minor deviation like sidecar_health still follows the resource-first convention. No mixing of styles or irregular verbs.
Tool Count5/5
19 tools cover multiple subsystems (leases, state, workflows, sessions, admin) without redundancy. Each tool has a clear role, and the count feels appropriate for the stated purpose of a sidecar server managing distributed state and workflow coordination.
Completeness4/5
The tool surface covers CRUD for state store, lease lifecycle, workflow creation and resumption, and admin operations. Minor gaps include no explicit tool to mark a workflow as failed/completed (only implied through checkpointing) and no update/delete for sessions. Overall, core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues