Integrate
Model Context Protocol (MCP)
Connect Reactive Skills as a stdio tool server for GUI agent environments and host-integrated tool workflows.
MCP as a host-integrated transport
The Model Context Protocol (MCP) enables GUI agent hosts to interact with external tools over JSON-RPC. Use it when the host provides MCP tool integration or when a persistent stdio bridge fits the workflow.
Local-first runtime selection
During INIT, Reactive Skills checks MCP and AXI capabilities and versions, then selects one compatible local transport for the run. AXI remains available through a direct command or its npx zero-install launcher.
When attached, the Reactive Skills MCP server exposes 10 tools for state inspection, signal emission, query execution, sync distribution, and migration, alongside append-only event resources.
Start the stdio server
npx -y @reactive-skills/axi mcpreactive-skills-axi mcp · listening on stdio
registered 10 tools · 3 resources
readyConfigure Cursor or VS Code
Add the server definition to your client’s MCP settings configuration file.
{
"mcpServers": {
"reactive-skills": {
"command": "npx",
"args": ["-y", "@reactive-skills/axi", "mcp"]
}
}
}Configure Claude Desktop
Claude Desktop consumes the same stdio server definition inside its config file.
{
"mcpServers": {
"reactive-skills": {
"command": "npx",
"args": ["-y", "@reactive-skills/axi", "mcp"]
}
}
}Registered tools and capabilities
- reactive_state — read the active state, active path, and context snapshot.
- reactive_emit_signal — dispatch a typed signal into the bus to advance the FSM.
- reactive_query — run structured queries against the skill state and event ledger.
- reactive_query_events — bounded replay of the append-only event stream.
- reactive_inspect — inspect statecharts, transitions, and guard contracts.
- reactive_invoke_skill — invoke and orchestrate child skills.
- reactive_respond_human — respond to Human-in-the-Loop (HITL) review gates.
- reactive_reset — reset active execution run while preserving deliverables.
- reactive_sync — synchronize skills across authoring workspaces and agent satellites via zero-drift junctions.
- reactive_migrate — apply schema migrations and WAL recovery to event stores.
Structured failure diagnostics
When a guard check or transition fails, the server returns structured error metadata rather than raw stack traces. Each failure specifies what invariant failed and the concrete remediation action.
Example recovery payload
Guard "exit_code == 0" evaluated to false on signal TEST_RAN — recovery: inspect failure output in events ledger, apply code fix, and re-emit TEST_RAN.