MCP server

Flightbox is itself MCP-native — your agents can drive the platform.

Claude Code / Desktop / Cursor (stdio):

claude mcp add flightbox -- uv run flightbox mcp

Streamable HTTP: every server exposes MCP at /mcp/ (stateless). Outside dev mode it requires your API key:

claude mcp add --transport http flightbox https://flightbox.co/mcp/ \
  --header "X-API-Key: fb_…"

Tools operate on the org that owns the key — tenant-isolated like the REST API.

Tools: list_suites, create_suite(name, spec_yaml), run_suite(suite_id, agents?, k?, base_url?), batch_status(batch_id), run_transcript(batch_id, run_id), run_telemetry(batch_id, run_id), generate_pdf(batch_id).

A nice loop: point your coding agent at a failing batch — it reads the transcript + telemetry via MCP, patches your site, redeploys, and reruns the suite. Agents fixing sites for agents.