Statecli MCP server

Read from the package source without running it. The installed server may list more.

• statecli_analyze_dependencies

  Analyze what files depend on a given file. Shows impact of changes.

• statecli_analyze_error

  Analyze an error and get recovery suggestions. Use when something goes wrong.

• statecli_auto_recover

  Automatically recover from an error using the best suggestion.

• statecli_checkpointwrite action

  Create named checkpoint before making changes. Use before risky operations.

• statecli_dependency_tree

  Get dependency tree for a file.

• statecli_file_history

  Get change history for a specific file.

• statecli_find_circular

  Find circular dependencies in the project.

• statecli_git_checkpointwrite action

  Create a checkpoint at current git state.

• statecli_git_history

  Compare changes between two commits.

• statecli_git_status

  Get current git status and track it.

• statecli_is_safe

  Check if a proposed change is safe to make.

• statecli_log

  View state change history for an entity.

• statecli_memory_query

  Query memory across sessions. Ask about past actions.

• statecli_predict_impact

  Predict impact of a proposed change. Shows affected files and breaking changes.

• statecli_preview_undo

  Preview what will happen if you undo N steps. Shows diff before executing.

• statecli_recent_activity

  Get summary of recent activity.

• statecli_replay

  Replay state changes for an entity. Shows step-by-step what happened with diffs.

• statecli_run_testswrite action

  Run tests and track results. Correlates with recent code changes.

• statecli_safe_change_orderwrite action

  Get recommended order for changing multiple files safely.

• statecli_safe_executewrite action

  Create checkpoint, execute operation, auto-rollback on error.

• statecli_session_info

  Get information about current and past sessions.

• statecli_simulate_undo

  Simulate undo without executing. Shows resulting state and side effects.

• statecli_suggest_tests

  Suggest which tests to run based on recent changes.

• statecli_test_impact

  Analyze which tests are affected by a changed file.

• statecli_track

  Explicitly track a state change.

• statecli_track_file

  Track a file edit with before/after content. Auto-generates diff.

• statecli_undo

  Undo state changes. Rollback when something went wrong.

• Code scan45 source files scanned20/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 qualitylocal package, no credentials required12/15
• Maintenancelast push 177 days ago8/15
• Maintainer identitynamespace and repository owner differ4/10

Safety score

68/100

higher than 30% of 48,255 servers

Tools

27

the typical server has 7

Tools that change things

19%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

2

more than 75% of 28,688 servers

Statecli: common questions

Is Statecli MCP server safe?

With care: it is graded C, so read the findings first (68/100). Read the Statecli safety report

How do I install Statecli?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Statecli need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Statecli maintained?

The last commit was 211 days ago (2026-04-07). The latest release is v0.5.0.

How does Statecli compare with other MCP servers?

safety score 68/100 (higher than 30% of 48,255 servers); tools 27 (the typical server has 7); tools that change things 19% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.