Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP State Sidecar: durable state persistence for multi-agent AI workflows
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"state-sidecar": {
"command": "uvx",
"args": [
"mcp-state-sidecar"
]
}
}
}在终端中运行这条命令
claude mcp add state-sidecar -- uvx mcp-state-sidecar粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"state-sidecar": {
"command": "uvx",
"args": [
"mcp-state-sidecar"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"state-sidecar": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-state-sidecar"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 askadvaith 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, MemberVault MCP by usefulapi
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
List courses; add users to courses, remove course access or delete users in MemberVault.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
2. Install build dependencies:
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.state_list(prefix?): List all live keys, optionally filtered by prefix.workflow_create(name, tags?): Register a workflow; returns a unique run_id.workflow_discover(tags?, status?): Find workflows filtered by tags or status.workflow_claim(run_id, agent_id): Atomically claim a created workflow.workflow_checkpoint(run_id, step, output): Persist step output and advance the step counter.workflow_resume(run_id): Get full resume context including last step and all step outputs.workflow_status(run_id): Get lightweight status (status, last step, and timestamps).workflow_list(): List all registered workflows.lease_acquire(resource_id, holder_id, ttl_seconds): Attempt to acquire an exclusive lock.lease_release(resource_id, holder_id): Voluntarily release a held lease.lease_renew(resource_id, holder_id, ttl_seconds): Extend lease duration without releasing.session_save(session_id, context): Save a snapshot of workflow context.session_restore(session_id): Retrieve saved context after crash or handoff.history_log(key?, n?): Retrieve the last N state-transition records with timestamps and writer IDs.sidecar_health(): Liveness, backend type, uptime, and database metrics.sidecar_reset(): Irreversibly wipe all data.This project is licensed under the MIT License. See LICENSE for details.