State Machine Designer MCP tool
findutils:state_machine_designer Validate a finite state machine given as nodes and edges and return a normalized machine config plus issues. Checks for missing ids, dangling transitions, duplicate labels, missing or multiple initial states, unreachable states, and outgoing transitions from final states. The config matches the designer's "Export Code" output ({ id, initial, states: { State: { EVENT: Target } } }).
Arguments
application/json-
nodes
array required
States: [{ id, data: { label, stateType: initial|normal|final, description? } }]. Flat { id, label, stateType } objects are also accepted.
-
edges
array required
Transitions: [{ source, target, label }] where label is the event name (uppercased in the config; "EVENT" when missing).
-
machine_id
string optional
Id written into the config. Default: "stateMachine". Default
"stateMachine".
Example arguments
Verified{
"nodes": [
{
"id": "s1",
"data": {
"label": "Idle",
"stateType": "initial"
}
},
{
"id": "s2",
"data": {
"label": "Done",
"stateType": "final"
}
}
],
"edges": [
{
"source": "s1",
"target": "s2",
"label": "FINISH"
}
]
}More Validation tools
- Email Validate Validate an email address and report every rule it breaks and break it into local / domain / TLD parts.
- Html Formatter Format (beautify) or minify HTML and return the result with a tag-balance validation report.
- Json Validate Validate a JSON string.
- Openapi Validator Validate an OpenAPI 3.x (or Swagger 2.0) document given as JSON or YAML and return a report with errors, warnings, and summary info (title…
- Phone Format Validate a phone number and format it as E.164 (+CCNNN…), international and national, using libphonenumber metadata for every country.
- Url Validate Validate that a string is a well-formed URL and (optionally) require HTTPS.