Snapstate MCP server
io.github.timbassler88/snapstate·v1.0.2·7 starsPersistent state for AI agent workflows. Save, resume, and replay multi-step workflows.
7 stars
Reviews
Write oneNobody has reviewed Snapstate yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Snapstate tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan2 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 qualitystatic API keys via environment variables6/15
- Maintenancelast push 166 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Snapstate compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 40% of 4,460 AI and agents servers
- GitHub stars
- 7
- more than 81% of 2,711 AI and agents servers
Install Snapstate in Claude Code, Cursor or VS Code
Runs npx -y snapstate-sdk on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add snapstate -- npx -y snapstate-sdk
What the publisher says
From the Snapstate repository's README, as published. We do not edit it. Read it on GitHub
MCP Registry
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
Development Status
2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).
Current key maintainers:
- Adam Jones (Anthropic) @domdomegg
- Tadas Antanavicius (PulseMCP) @tadasant
- Toby Padilla (GitHub) @toby
- Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov
Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
- Discord - Real-time community discussions
- Discussions - Propose and discuss product/technical requirements
- Issues - Track well-scoped technical work
- Pull Requests - Contribute work towards issues
Quick start:
Pre-requisites
- Docker
- Go 1.24.x
- ko - Container image builder for Go (installation instructions)
- golangci-lint v2.4.0
Running the server
# Start full development environment
make dev-composeThis starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRY_VALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Alternative: Running a pre-built Docker image
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Snapstate: common questions
- Is Snapstate MCP server safe?
- Mostly: it is graded B (72/100). Read the Snapstate safety report
- How do I install Snapstate?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Snapstate need an API key?
- Yes. The registry entry asks for
SNAPSTATE_API_KEY. - Is Snapstate maintained?
- The last commit was 203 days ago (2026-04-15). The latest release is v1.0.2.
- What can I use instead of Snapstate?
- Servers from other publishers that do the same job: Claude Prompts MCP server, PaperBanana MCP server and Memanto MCP server.
- How does Snapstate compare with other AI and agents MCP servers?
- safety score 72/100 (higher than 40% of 4,460 AI and agents servers); github stars 7 (more than 81% of 2,711 AI and agents servers). Full comparison.
Alternatives to Snapstate
Same job from other publishers: the closest match first, then the best rated.
- Claude PromptsReusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.not reviewedEstablishedA
- PaperBananaGenerate academic diagrams and statistical plots from text using multi-agent AI.not reviewedEstablishedA
- MemantoMCP server for Memanto - persistent semantic memory for any MCP-compatible agentnot reviewedEstablishedA
World Model MCPPersistent 3D/2D spatial world model for AI agents with dynamic velocity and entity tracking.not reviewedEstablishedA- Godot MCPAgent-driven Godot playtesting: editor control, input injection, game-time stepping, live state.not reviewedEstablishedA
