All servers / Developer / Stately MCP server
Stately MCP server
Reusable Stately MCP server for XState machine tooling.
Tested by ConnectATDScore 83 out of 100. Tested 2026-11-18 on package version 0.29.6. Package: @statelyai/mcp
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 13 / 20 | |
| Package safety | 16 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.9 seconds including download)
- Tools offered: 22
- Last published: 2026-11-17
- Weekly downloads (npm): 35,280
- License: SEE LICENSE IN LICENSE · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_machines0 of 1 parameter describedList candidate machine sources in the workspace.
get_machine0 of 2 parameters describedRead a machine source from the workspace and return it.
visualize_machines0 of 3 parameters describedVisualize several models in one temporary workspace without saving hosted models. Reuse the returned workspaceId and stable machineIds for subsequent additions, updates and retries. Background additions preserve selection. selectedMachineId explicitly opens a model. Source conversion is structural, not executable verification.
read_visualization_workspace0 of 1 parameter describedReopen a temporary visualization collection, including selection, draft edits and revision history. Does not save models to hosted projects.
update_visualization_workspace1 of 4 parameters describedPersist temporary draft edits and selection with optimistic concurrency. Never writes hosted models.
validate_machine0 of 3 parameters describedDeterministically validate machine syntax and graph structure. This does not typecheck or execute XState source; use simulate_machine and generate_graph_paths to verify runtime behavior.
convert_machine0 of 4 parameters describedConvert XState, JSON machine configs, SCXML, XGraph, Mermaid, or D2 input to XState, SCXML, XGraph, or D2 through the Stately API.
diff_machines0 of 3 parameters describedCompute a semantic diff between two machine documents through the Stately API.
apply_machine_patches0 of 5 parameters describedCreate a non-mutating behavioral proposal by applying semantic machine patches in memory through the Stately API. Returns the updated document, the structured patches, and a concise behavioral summary; it never writes files or invokes Git. Use graph entity IDs: top-level XState states commonly use <machine-id>.<state-key> (for example job.running). Use camelCase operations such as createTransition, not snake_case names.
review_machine_implementation0 of 3 parameters describedDeterministically review an agent-edited machine against a non-mutating semantic patch proposal. Reports validation issues plus missing, extra, or divergent behavior and returns a portable Markdown review artifact with before/after Mermaid graphs. It never writes files or invokes Git.
generate_graph_paths0 of 7 parameters describedGenerate shortest or simple paths through the Stately API. XState source must be complete executable source (including imports) because it runs natively in an isolated sandbox. max sets page size (default 5, maximum 1000); pass nextCursor as cursor with the same input to retrieve more. Pagination distinguishes complete bounded generation from budget exhaustion; it does not establish application coverage.
simulate_machine0 of 6 parameters describedSimulate a machine through events. XState source runs in an isolated sandbox. SCXML defaults to structural mode; executionMode="native" opts into sandboxed XState v6 execution. advanceTimeMs runs virtual timers after the supplied events. Returns execution metadata and optional completion output.
check_machine0 of 5 parameters describedCheck a native statechart (XGraph or XState config) against a rules file with the bounded native explicit-state checker: never, initially, eventually, eventually-always, leads-to, no-dead-ends and reachable rules over hierarchical and parallel states and bounded context. Returns per-rule verdicts with native counterexample traces and a graph carrying the check report; save it with save_stately_check_result. Undecidable results are not-checked. Runs on the hosted API with bounded time and state limits; for TLA+ use the /stately skill's stately-check command.
export_machine_image0 of 7 parameters describedExport a machine as a PNG or SVG image. Returns PNG as an image content block, or SVG markup as text. Supports XState, JSON, XGraph, SCXML, Mermaid, D2, and Digraph sources.
visualize_machine0 of 11 parameters describedVisualize XState source text (the default for strings), JSON machine configs, SCXML, XGraph, Mermaid, or D2. Returns a View in Stately link; hosts that support MCP Apps also render an interactive hierarchy graph inline, and other hosts get directly viewable PNG fallbacks. Optionally select a root view, request multiple parent views, or recompute fallback layout.
extract_machines_from_code1 of 2 parameters describedDeterministically extract canonical XState machine configs from JavaScript or TypeScript source. XState 5/6 syntax is inferred unless explicitly provided.
report_visualization_renderedno parametersRecord that the interactive visualization rendered successfully.
visualize_stately_machine0 of 5 parameters describedFetch and visualize one hosted Stately machine. Returns a View in Stately link; hosts that support MCP Apps also render an interactive hierarchy graph inline, with directly viewable PNG fallbacks and optional root, parent, or layout controls.
list_stately_projectsno parametersList the hosted Stately projects the caller can access. Hosted resources only; use list_machines for workspace files.
get_stately_project1 of 1 parameter describedRead one hosted Stately project, including its current project version id and machine ids.
list_stately_project_machines1 of 1 parameter describedList the machines belonging to a hosted Stately project.
get_stately_machine1 of 1 parameter describedRead one hosted Stately machine, including its definition.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.