MCP State Sidecar: durable state persistence for multi-agent AI workflows
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-askadvaith-mcp-state-sidecar": {
"args": [
"mcp-state-sidecar"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP-native state sidecar that externalises workflow state for distributed agent deployments.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'mcp-state-sidecar' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-state-sidecar against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
An autonomous agent that conducts deep research on any data using any LLM providers
🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration
MCP Security Weekly
Get CVE alerts and security updates for io.github.askadvaith/mcp-state-sidecar and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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]
To build and install the package from source:
git clone https://github.com/askadvaith/MCP-State-Sidecar.git
cd MCP-State-Sidecar
pip install --upgrade build
python -m build
pip install dist/mcp_state_sidecar-*.whl
Or install the package in editable mode for active development:
pip install -e .
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.
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.
Launch the server via standard input/output:
mcp-state-sidecar
The server is configured entirely using environment variables:
| Environment Variable | Default | Description |
|---|---|---|
STATE_BACKEND | sqlite | Storage backend: sqlite or redis |
DB_PATH | state_sidecar.db | Path to the SQLite database file |
REDIS_URL | redis://localhost:6379 | Redis connection URL |
SIDECAR_HOST | 0.0.0.0 | IP host to bind the HTTP SSE server |
SIDECAR_PORT | 8000 | Port for the HTTP SSE server |
state_set(key, value, ttl_seconds?, agent_id?): Upsert a JSON-serialisable value with optional TTL.state_get(key): Retrieve a value (returns found=False if missing or expired).state_delete(key): Delete a key.