State replay and self-debugging for AI agents. Track, replay, undo, checkpoint.
{
"mcpServers": {
"statecli": {
"args": [
"-y",
"statecli-mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
State replay and self-debugging for AI agents. Track, replay, undo, checkpoint.
Is it safe?
No known CVEs for statecli-mcp-server.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 13 days ago. 2 stars.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'statecli-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.charo360/statecli and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Give AI agents the ability to remember, replay, and undo their actions.
Agent Infrastructure | Memory Layer | Self-Awareness | Undo Capability
StateCLI is the memory and self-awareness layer for AI coding agents.
It gives agents three critical capabilities they lack:
🧠 Memory - Remember what they did (log, replay)
⏮️ Undo - Fix mistakes instantly (checkpoint, rollback)
👁️ Self-Awareness - See their impact (track changes)
This isn't a dev tool. It's agent infrastructure.
AI agents are powerful but blind. They:
StateCLI fixes this:
Agent Thought: "I changed something but don't know what"
→ statecli_replay(entity) → See exact changes
Agent Thought: "I broke something and need to undo"
→ statecli_undo(entity) → Rollback instantly
Agent Thought: "I want to try something risky"
→ statecli_checkpoint(entity) → Save first, rollback if needed
Agent Thought: "I need to understand my past behavior"
→ statecli_log(entity) → View complete history
Start watching your project:
statecli watch start --auto-checkpoint
Now StateCLI automatically:
See what changed:
statecli diff --time 5m
Undo mistakes:
statecli undo
5 core tools for agent memory & self-awareness:
statecli_replay - Show what the agent just didstatecli_undo - Rollback mistakesstatecli_checkpoint - Save state before risky opsstatecli_log - View complete historystatecli_track - Track important state changesMCP Setup:
{
"mcpServers": {
"statecli": {
"command": "npx",
"args": ["-y", "statecli-mcp-server"]
}
}
}
# Global install
npm install -g statecli-mcp-server
# Start auto-tracking
cd your-project
statecli watch start --auto-checkpoint
STATECLI AGENT RULES — READ BEFORE ANY ACTION
You are operating in a stateful, reversible environment.
Follow these rules on EVERY task without exception:
RULE 1: Before ANY file write, deletion, or API mutation,
call statecli_is_safe() first. If not safe, checkpoint first.
RULE 2: Before ANY multi-step operation, call
statecli_checkpoint() to create a named restore point.
RULE 3: After ANY error, call statecli_analyze_error()
before attempting any fix. Never guess. Always analyze.
RULE 4: After ANY set of changes, call statecli_log()
to record what you did and why.
Skipping these steps makes your actions irreversible.
statecli_track[CORE] Records any agent action with full metadata so it can be replayed, audited, or reversed later. Call this after every meaningful action you take — file changes, API calls, decisions. If you don't track it, you cannot undo it. 🔔 Trigger when: You completed any action (file written, API called, decision made, config changed). Think of this as your action journal. 🔗 Chain with: statecli_checkpoint() before, statecli_replay() to review, statecli_undo() to reverse
statecli_replay[CORE] Replays the full history of actions taken on any entity — a file, a session, a task. Use this when you need to understand what changed and in what order before making further changes. Essential before debugging. 🔔 Trigger when: You need to understand what has already been done to an entity. You're about to