mcpbeat Sign in

Snapstate MCP Server

by timbassler88 Your server? Claim it
local only

Snapstate runs on your own machine — the client starts it, so there is no endpoint to ping. 36 installs a week from npm. Last commit 15 Apr 2026.

Persistent state for AI agent workflows. Save, resume, and replay multi-step workflows.

Installs per day peak 11 · avg 3 · +7% w/w
a month agotoday
36
Installs / week
npm · snapstate-sdk
7
Stars
0 open issues
15 Apr 2026
Last commit
no releases in 90 days
—
License
JavaScript

What the code does

We read the source, 7 d ago · rules 995398eba69f

In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Page executes code built at runtime server/src/get-started.html:830
  el.innerHTML = msg;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Nothing serious here today

Today is the operative word: we check Snapstate every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add snapstate -e 'SNAPSTATE_API_URL=<SNAPSTATE_API_URL>' -e 'SNAPSTATE_API_KEY=<SNAPSTATE_API_KEY>' -- npx -y snapstate-sdk
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "snapstate": {
      "command": "npx",
      "args": [
        "-y",
        "snapstate-sdk"
      ],
      "env": {
        "SNAPSTATE_API_KEY": "<SNAPSTATE_API_KEY>",
        "SNAPSTATE_API_URL": "<SNAPSTATE_API_URL>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.snapstate]
command = "npx"
args = ["-y", "snapstate-sdk"]
env = { SNAPSTATE_API_URL = "<SNAPSTATE_API_URL>", SNAPSTATE_API_KEY = "<SNAPSTATE_API_KEY>" }
.cursor/mcp.json
{
  "mcpServers": {
    "snapstate": {
      "command": "npx",
      "args": [
        "-y",
        "snapstate-sdk"
      ],
      "env": {
        "SNAPSTATE_API_KEY": "<SNAPSTATE_API_KEY>",
        "SNAPSTATE_API_URL": "<SNAPSTATE_API_URL>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "snapstate": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "snapstate-sdk"
      ],
      "env": {
        "SNAPSTATE_API_KEY": "<SNAPSTATE_API_KEY>",
        "SNAPSTATE_API_URL": "<SNAPSTATE_API_URL>"
      }
    }
  }
}

Put your own values in place of <SNAPSTATE_API_URL> (SnapState API URL), <SNAPSTATE_API_KEY> (Your SnapState API key (starts with snp_)). The author’s registry entry marks them as required.

Alternatives to Snapstate

same job, measured the same way
MCP State Sidecar
by askadvaith

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

96 installs/wk local only
agenthold
by edobusy

Shared versioned state for multi-agent AI workflows

270 installs/wk local only
GraphyLoop
by chadixearth

Workflow planner, wave dispatcher, persistent swarm memory, and deploy preflight for AI agents.

557 installs/wk local only
Argus Retrieval
by khamel83

Multi-provider search broker for AI agents: 14 providers, 12-step extraction, retrieval workflows.

201 installs/wk local only
MCP Agent Trace Inspector
by dbsectrainer

Step-by-step observability for MCP agent workflows

330 installs/wk local only
Moira
by moira-mcp

Agent Workflow Engine — multi-step MCP workflows with per-step directives and validation.

local only
Handoff MCP Server
by josephibra

Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.

3 tools answering
Claude Prompts MCP
by minipuft

Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.

118 installs/wk local only

Snapstate — questions

Answers built from our own checks of this server.

Why is there no uptime for Snapstate?
Snapstate runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package snapstate-sdk was installed 36 times last week.
How do I connect Snapstate?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls snapstate-sdk straight from npm; nothing to host, nothing to sign up for.
How many people use Snapstate?
The npm package snapstate-sdk was installed 36 times in the last week. Week over week that is +7%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Snapstate open source?
We cannot say either way: written in JavaScript and 7 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.