Because flows are plain text, an AI agent can genuinely work on them: read the YAML, run the
flow, see exactly which node failed and what it sent, edit the file, run again. The
Bandura MCP server (bandura-mcp) packages that loop as
Model Context Protocol tools for Claude Code, Cursor, and
any other MCP client.
It’s a stdio server over the same engine, parser, and importers as the app and CLI — no Electron, no network service, runs on your machine.
Connecting a client
Register bandura-mcp as a stdio server in your client. For Claude Code:
claude mcp add bandura -- bandura-mcpOr in a JSON-style MCP config:
{
"mcpServers": {
"bandura": {
"command": "bandura-mcp",
"env": { "BANDURA_WORKSPACE": "/path/to/your/api-tests" }
}
}
}The workspace root resolves in this order: a root argument on the tool call, the
BANDURA_WORKSPACE environment variable, or the server’s working directory.
The tools
| Tool | What it does |
|---|---|
list_flows | Enumerate the .aether files under the workspace root — path, name, node count. |
read_flow | Return a flow’s raw YAML. |
run_flow | Execute a flow and return structured results: per-node pass/fail, captured variables, and request/response snapshots sized for a model’s context (fullBody: true for untruncated payloads). Accepts variables overrides. ai-action nodes run when ANTHROPIC_API_KEY is set in the server’s environment. |
detect_drift | Compare a flow against an OpenAPI spec and return findings with proposed fixes — the same deterministic check as self-healing. |
import | Convert curl/OpenAPI/Postman source text into .aether — written to a directory or returned inline. |
What that enables
Ask your agent things like:
- “Run the checkout flow and tell me why it fails.” — the agent runs it, reads the failing node’s actual request and response, and reasons from ground truth instead of guessing.
- “Fix it.” — the flow is a text file; the agent edits it with its normal file tools and re-runs to verify.
- “Check all flows against openapi.yaml and fix the drift.” —
list_flows+detect_driftper flow, apply fixes, re-run.
The results the agent sees are the same results you see in the editor’s Result tabs — one engine, one file format, three ways in (app, CLI, agent).