mcp-swarm-analyseAnalyse a failed botz MCP Swarm run with the configured model, review its proposed suite fixes one by one, and accept or reject them by explicit proposal id. Nothing changes without a named id.
mcp-swarm-compareCompare two botz MCP Swarm runs or a series of runs and visualise latency, error rate, and tool-eval trends in Cursor's /canvas or a self-contained HTML page. Use to check for regressions between builds, environments, or load settings.
mcp-swarm-descriptionsReview an MCP server's tool descriptions, propose clearer ones, examine description suggestions saved by botz MCP Swarm optimize, and measure a description change with tool evals. Use when models pick the wrong tool, misuse arguments, or a server's descriptions need an audit.
mcp-swarm-diagnoseDiagnose failed botz MCP Swarm suites, missing credentials, invalid fixtures, execution errors, and performance regressions from CLI diagnostics and run reports.
mcp-swarm-flowTurn a task described in words, such as "find an open bug in GitHub, file it in Jira, tell #triage", into a botz MCP Swarm suite whose steps call several MCP servers in order and pass values between them. Use to load-test or regression-test an agent-like workflow that spans MCP servers.
mcp-swarm-guidedGuided, question-driven introspection of an MCP server with botz MCP Swarm, from target and credentials through suite generation, review, and execution to a summarised result. Use when someone wants to test an MCP server and has not set up a suite yet.
mcp-swarm-platformOpt in to Botz MCP Swarm platform mode and use its features (central swarm MCP server with OAuth, remote suite runs, worker dispatch, service suites, swarm_* MCP tools). Use only when the user explicitly enables platform mode or BOTZ_MCP_SWARM_MODE=platform is set.
mcp-swarm-record-replayRecord redacted MCP wire traffic from a server with botz MCP Swarm and replay it against the same or another server, as recorded, at maximum rate, or paced. Use to reproduce a session, compare server builds on identical traffic, or create fixtures.
mcp-swarm-reportVisualise one botz MCP Swarm run in Cursor's /canvas or a self-contained HTML page, with a tool selector showing each tool's latency, errors, and a sample request and response. Use after a run, or to explain a run report.
mcp-swarm-server-updatesCheck MCP servers under test for updates (serverInfo version, negotiated MCP spec/protocol version, capabilities, and every tool, resource, template and prompt schema), review the diff, surgically update only the suites and scenarios that reference changed primitives, and record a changelog entry on
mcp-swarm-tagsEdit descriptions on MCP Swarm suites and servers, and add ad-hoc tags to suites, scenarios and runs, then filter lists by tag from the local CLI.
mcp-swarm-upgradeUpgrade the botz MCP Swarm CLI and move saved suites, credentials, run reports, and service state into the current layout. Use when updating MCP Swarm, after release notes mention moved files, or when old .botz/suites, .runs, .swarm-data, or .otel directories are present.
mcp-swarmCapture, validate, refresh, and run MCP test suites entirely locally with the botz MCP Swarm CLI (no central Swarm server, no MCP server config). Use for testing MCP servers, repeatable tool assertions, local load tests, and CI reports.