MCP.Market

State Sidecar MCP server

by askadvaith·io.github.askadvaith/mcp-state-sidecar·v0.1.0·7 stars
No reviews yet

MCP State Sidecar: durable state persistence for multi-agent AI workflows

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

7 stars

Reviews

Write one

Nobody has reviewed State Sidecar yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

State Sidecar tools (19, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • history_log

    Return the last N state-transition records in reverse chronological order.

  • lease_acquire

    Try to acquire an exclusive, TTL-based lease on a named resource.

  • lease_release

    Voluntarily release a lease this agent holds.

  • lease_renew

    Extend an existing lease's TTL while still holding it.

  • session_restore

    Retrieve the workflow context saved for a session_id.

  • session_save

    Persist the full workflow context for a session_id.

  • sidecar_health

    Check sidecar liveness and get backend diagnostics.

  • sidecar_reset

    Wipe all sidecar state: kv_store, leases, workflows, step_outputs, history, and sessions.

  • state_deletewrite action

    Delete a key from the state store.

  • state_get

    Get the value stored under *key*.

  • state_list

    List all live (non-expired) keys, optionally filtered by prefix.

  • state_set

    Set a key-value pair in the shared state store.

  • workflow_checkpoint

    Atomically persist a completed step's output and advance the step counter.

  • workflow_claim

    Atomically claim a workflow for this agent.

  • workflow_createwrite action

    Register a new workflow and get back a unique run_id.

  • workflow_discover

    Find workflows available for a worker to pick up.

  • workflow_list

    List all registered workflows (all statuses).

  • workflow_resume

    Get everything a replacement agent needs to resume a crashed workflow.

  • workflow_status

    Get the current status of a workflow — lightweight alternative to workflow_resume.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan10 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 106 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How State Sidecar compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 65% of 4,460 AI and agents servers
Tools
19
the typical AI and agents server has 6
Tools that change things
11%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
7
more than 81% of 2,711 AI and agents servers

What its tools let an agent do: 17 read · 2 change

Install State Sidecar in Claude Code, Cursor or VS Code

claude mcp add mcp-state-sidecar -- uvx mcp-state-sidecar
Add to Cursor

What the publisher says

From the State Sidecar repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.askadvaith/mcp-state-sidecar -->

MCP State Sidecar Server

An MCP-native state sidecar that externalises workflow state for distributed agent deployments.

Quite a simple idea really; instead of storing state inside agents (which breaks when processes crash, scale horizontally, or span multiple frameworks), agents write to and read from this sidecar over the Model Context Protocol (MCP). The sidecar is itself an MCP server; agents call its tools exactly the same way they call any other tool!

The server itself is built with distributed environments in mind, and natively handles concurrency, crash resilience and atomic claims in addition to being a common interface for state management between agents.

Features

  • Durable Key-Value Store: CRUD operations with optional TTL (Time-To-Live).
  • Workflow Lifecycle Registry: Centralised coordination (create, claim, checkpoint, and resume) for distributed multi-agent workers without out-of-band communication.
  • TTL Leases & Locks: Concurrency control to prevent race conditions and split-brain scenarios.
  • Audit Logging & Session Snapshotting: Audit state transitions and persist session contexts.
  • Multiple Backends: SQLite (with WAL mode & serialisation) and high-concurrency Redis currently supported.

Installation

Install the package via pip or your favorite Python package manager:

pip install mcp-state-sidecar

If you want to use the Redis backend:

pip install mcp-state-sidecar[redis]

Building from Source

To build and install the package from source:

  1. Clone the repository:
git clone https://github.com/askadvaith/MCP-State-Sidecar.git
   cd MCP-State-Sidecar
  1. Install build dependencies:
pip install --upgrade build
  1. Build the wheel and source distribution:
python -m build
  1. Install the package locally:
pip install dist/mcp_state_sidecar-*.whl

Or install the package in editable mode for active development:

pip install -e .

Quick Start

Running the Server

In a multi-agent distributed environment, you would typically run the state sidecar as an HTTP SSE service so multiple remote agents and clients can connect to it concurrently.

HTTP SSE Mode (Primary for Distributed Environments)

Start the SSE server to listen on a network port:

mcp-state-sidecar-http

By default, the server binds to 0.0.0.0 and listens on port 8000. The MCP endpoint is available at http://localhost:8000/mcp.

Stdio Mode (For Subprocess / Local Agent Execution)

Launch the server via standard input/output:

mcp-state-sidecar

Configuration

The server is configured entirely using environment variables:

Tool Reference

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

State Sidecar: common questions

Is State Sidecar MCP server safe?
Mostly: it is graded B (82/100). Read the State Sidecar safety report
How do I install State Sidecar?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does State Sidecar need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is State Sidecar maintained?
The last commit was 145 days ago (2026-06-12). The latest release is v0.1.0.
What can I use instead of State Sidecar?
Servers from other publishers that do the same job: PaperBanana MCP server, Agent-Native Chat MCP server and Godot MCP server.
How does State Sidecar compare with other AI and agents MCP servers?
safety score 82/100 (higher than 65% of 4,460 AI and agents servers); tools 19 (the typical AI and agents server has 6); tools that change things 11% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to State Sidecar

Same job from other publishers: the closest match first, then the best rated.

  • PaperBanana
    Generate academic diagrams and statistical plots from text using multi-agent AI.
    A
  • Agent-Native Chat
    Minimal chat-first app with durable threads, actions, and the app-agent loop
    A
  • Godot MCP
    Agent-driven Godot playtesting: editor control, input injection, game-time stepping, live state.
    A
  • three.ws Brain
    List LLM providers and run chat completions through the three.ws multi-provider router.
    More from nirholas →
    B
  • Claude Prompts
    Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.
    A