Stateark MCP server

StateArk

Never explain your project to an AI twice.

Your chat is a workspace, not an archive. StateArk turns a working session into a versioned, portable project state that any new chat can pick up. Open terminal and write:

npx stateark

Then quit Claude Desktop completely (Cmd+Q) and reopen it. That is the whole install.

(Prefer to install from source? npm install && npm run build && npm run setup — see INSTALL.md. Undo any time with npx stateark remove.)

Here what we had in mind developing stateark - we address a problem millions of users have...

You:  ...three hours of work...
You:  Savepoint
      -> my-project v0.3 written to ~/StateArk

      (next day, new chat, empty context)

You:  Resume my-project
      -> decisions, constraints, rejected approaches, open questions,
         and the actual files - all current, none of the detours

Local by default. Savepoints are ordinary folders of Markdown, JSON and your real files. Nothing is uploaded. If StateArk disappears tomorrow, you still have everything.

~/StateArk/projects/my-project/v0.3/
  state.md        <- the canonical state, readable in any editor
  state.json
  manifest.json   <- every artifact with its SHA-256
  artifacts/
    app.py
    schema.sql

Commands

What makes it more than a summary

their original hash, so a forgetful model cannot silently lose your schema.

• Carry-forward. Files you do not re-submit are copied into the new version with

truncation markers (// ... rest unchanged), files that collapsed in size, files the state describes but never handed over, savepoints identical to their predecessor. It warns, it never blocks: the savepoint is always written.

• Integrity checks. StateArk cannot see your chat - so it checks what it can:

Savepoint at the end of a long session does not depend on a degraded context. Only for projects you already saved once - scratch conversations are never touched.

• Journal. Between savepoints the model quietly records turning points, so a

Requirements

Node 20+. Claude Desktop, or Claude Code (claude mcp add --transport http ...). It also runs under other local MCP hosts — users have it working with Codex and Hermes against the same store.

Hosted clients that dial your server from the vendor's cloud (Claude web, ChatGPT web) cannot reach localhost. See INSTALL.md.

Several agents at once

Supported, and worth saying plainly because it is the setup that broke first. Writes to a project are serialised across processes, so two agents cannot claim the same version number. If a savepoint reports that another process is busy, repeat it in a moment — nothing is lost. A process that dies mid-write releases its lock automatically.

If your store lives in Dropbox, OneDrive or iCloud Drive: several agents on one machine are fine. Two machines writing the same store simultaneously is a sync conflict, which the sync client resolves and StateArk cannot.

Licence

Shortened. The full README is on GitHub.