MCP servers · askrion

StateArk: versioned project-state savepoints for AI chats

A local MCP server that saves a working session as a versioned savepoint and loads it into a new chat.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

StateArk saves a working session with an AI assistant as a versioned savepoint: a folder of Markdown, JSON and the project's own files. Inside a chat, Savepoint writes a new version, Resume loads the latest state into a fresh chat, History lists versions, and Diff shows what changed between two savepoints. Files not re-submitted are carried into the new version with their original hash. Integrity checks flag truncation markers, sharply shrunk files, files the state describes but were not supplied, and savepoints identical to their predecessor. These checks warn but never block a save.

It suits projects that run across many chats, or that several agents work on at once. Writes are serialised across processes so two agents cannot claim the same version number, and a busy savepoint can be retried. Stores kept in Dropbox, OneDrive or iCloud Drive support several agents on one machine.

Running it requires Node 20+ and registration with Claude Desktop or Claude Code. By default, nothing leaves the machine and the store is a local folder; Supabase sync is opt-in. Unregistering keeps existing savepoints.

Limitations and requirements

Requires Node 20+ and a local MCP host such as Claude Desktop or Claude Code. Hosted clients (Claude web, ChatGPT web) cannot reach localhost, and remote access is not yet available. Licensed under Elastic License 2.0: it may not be offered to third parties as a hosted or managed service. Two machines writing the same synced store at once cause a sync conflict that StateArk cannot resolve. Supabase sync needs the migrations run and a server-side Secret key. A non-loopback bind requires an access key of at least 24 characters. Exposing the agent over HTTPS requires a reverse proxy and a long access key.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Askrion/stateark

    Local-first version control for AI work. Savepoint and resume your project state across chats.

    v0.5.3
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 17 Nov 2026