StateJar memory

com.statejarPublished by statejar.comOfficial publisherv1.0.0Updated Oct 30, 2026

Verifiable memory for AI assistants: typed facts, content-addressed versions and an audit trail.

VerifiedStreamable HTTPWeb executableKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

Hosted memory layer for AI assistants that stores typed, versioned facts with an audit trail and verifiable handles.

What you can do
  • Store, search, get, list and update typed facts that are checked against their type
  • Delete facts, review version history and export stored state
  • Inspect an audit trail of disclosures and verify a state's SHA-256 handle
  • Keep facts instead of transcripts, with secrets stripped before anything is sent
When to use it
Use it when an assistant should carry durable, checkable facts across sessions rather than replaying conversation transcripts, or when you need an auditable record of what memory was disclosed.
Requirements
Remote MCP endpoint over HTTP with an Authorization header carrying a StateJar developer key (Bearer sj_live_…), created in the StateJar account; network access to the hosted server and API.
Before you install
Requires a StateJar developer key scoped to your account, sent as the Authorization header; the service is hosted and paid tiers are referenced, so check pricing. Tools can write, update and delete stored facts, and memory content is sent to StateJar's servers.

Installation

In SourceWeft

  1. Open StateJar memory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.statejar%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "statejar-memory": {
      "type": "http",
      "url": "https://statejar.com/mcp"
    }
  }
}

README

StateJar integrations: memory your AI agents can trust

[PyPI] [npm]

statejar.com · Docs · Blog · Pricing

Client code that connects AI coding agents and assistants to StateJar, a memory layer that keeps facts instead of transcripts. Each value is checked by its type (a value that fails is refused, with a reason), every change is a new version with the old one kept in history, an assistant gets only the facts a question needs, every disclosure is audited, and each state has a verifiable handle (shm_…, the SHA-256 of the canonical state).

Quick start

  1. Make a developer key at https://statejar.com/api-keys and set STATEJAR_API_KEY.
  2. Pick your client:
ClientInstall
Claude Codeclaude plugin marketplace add KING-OF-FLAME/statejar-integrations then claude plugin install statejar@statejar
Codexcodex plugin marketplace add KING-OF-FLAME/statejar-integrations then codex plugin add statejar@statejar
OpenCode"plugin": ["opencode-statejar"] in opencode.json
Hermes Agenthermes plugins install KING-OF-FLAME/statejar-integrations/hermes/statejar --enable
OpenClawopenclaw plugins install openclaw-statejar
Any MCP clientremote MCP server https://statejar.com/mcp, header Authorization: Bearer <key>

Details for each are below.

What is here

  • Hosted MCP server, for any client that speaks MCP over HTTP: https://statejar.com/mcp (live).
  • Claude Code plugin: plugins/statejar/; guide in claude-code/. Marketplace: this repository.
  • Codex plugin (the same plugin): guide in codex/. Marketplace: this repository.
  • OpenCode plugin: opencode/. npm: opencode-statejar.
  • Hermes Agent memory provider (memory.provider: statejar): hermes/statejar/. Install with hermes plugins install from this repository.
  • OpenClaw memory-slot plugin: openclaw/. npm: openclaw-statejar.
  • Agent skill, for any agent that reads SKILL.md: skills/statejar/.
  • CLI: pip install statejar gives statejar login, init, add, search, list, forget, export, status.

Every integration uses a StateJar developer key (https://statejar.com/api-keys), scoped to your account. None of them stores a transcript. Each removes secrets before anything is sent.

Availability. Recall and capture call StateJar's REST API at https://api.statejar.com. The plugins' StateJar tools use the hosted MCP server at https://statejar.com/mcp. Both are live.

Any MCP client

Make a developer key at https://statejar.com/api-keys and put it in STATEJAR_API_KEY. Then:

bash
# Claude Codeclaude mcp add --transport http statejar \  https://statejar.com/mcp \  --header "Authorization: Bearer $STATEJAR_API_KEY"
# Codexcodex mcp add statejar \  --url https://statejar.com/mcp \  --bearer-token-env-var STATEJAR_API_KEY

OpenCode, in opencode.json:

json
{  "mcp": {    "statejar": {      "type": "remote",      "url": "https://statejar.com/mcp",      "oauth": false,      "headers": { "Authorization": "Bearer {env:STATEJAR_API_KEY}" }    }  }}

Any other client: a remote (HTTP) MCP server at https://statejar.com/mcp with the header Authorization: Bearer <your key>. The ten tools are remember, search, get, list, update, delete, history, audit, verify and export.

Claude Code

bash
claude plugin marketplace add KING-OF-FLAME/statejar-integrationsclaude plugin install statejar@statejar

See claude-code/README.md.

Codex

bash
codex plugin marketplace add KING-OF-FLAME/statejar-integrationscodex plugin add statejar@statejar

Then trust the plugin's hooks with /hooks. See codex/README.md.

OpenCode

Add "plugin": ["opencode-statejar"] and StateJar's MCP server to opencode.json. See opencode/README.md.

Hermes Agent

bash
hermes plugins install KING-OF-FLAME/statejar-integrations/hermes/statejar --enablehermes memory setup          # choose statejar

See hermes/statejar/README.md.

OpenClaw

bash
openclaw plugins install openclaw-statejaropenclaw statejar init       # the memory slot, autoRecall, autoCapture

See openclaw/README.md.

Agent skill

Copy skills/statejar/ into your agent's skills folder (for Claude Code, ~/.claude/skills/). See skills/README.md.

Tests

bash
python -m pytest tests/claude plugin validate ./plugins/statejarclaude plugin validate .

End to end, against a local or staging StateJar (never production): a fact stated in one session of the real client is recalled in a fresh one, through the hooks and through StateJar's MCP tools. Each run makes a throwaway account and deletes it. With no model on the machine, a scripted stand-in (e2e/scripted_model.py) answers "OK" or calls StateJar's search and repeats its output verbatim; codex_e2e.py --model ollama:<name> uses a real local model.

Each script takes the API (and, where it uses MCP, the MCP URL) of a local or staging server, and an output folder:

bash
API=http://127.0.0.1:8000/api/v1MCP=http://127.0.0.1:8000/mcp
python e2e/codex_e2e.py --api $API --mcp $MCP --out /tmp/codex-e2epython e2e/claude_code_e2e.py --api $API --mcp $MCP --out /tmp/cc-e2epython e2e/opencode_e2e.py --api $API --mcp $MCP --out /tmp/oc-e2epython e2e/hermes_e2e.py --api $API --out /tmp/hermes-e2epython e2e/openclaw_e2e.py --api $API --out /tmp/openclaw-e2e
  • openclaw_e2e.py needs Node 24.16+.
  • python e2e/openclaw_discovery.py and python e2e/codex_discovery.py show what OpenClaw and Codex themselves load from the plugin (no model, no StateJar).
  • HERMES_PYTHON=/path/to/hermes/venv/bin/python python -m pytest tests/test_hermes_provider.py runs the provider test with Hermes's own loader.

Licence

MIT (see LICENSE). The StateJar service these clients talk to has its own terms: https://statejar.com/terms.

Source: README.md at commit 33a3226

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts