The Blazing MCP server implements the Model Context Protocol, making the developer platform queryable by any MCP-compatible coding agent. External tools — Claude Code, Cursor, GitHub Copilot, and others — can ask questions about infrastructure state without leaving the IDE.

Exposed capabilities include deployment status and history, container logs, resource usage, SDL config for any active workload, and cluster health. The server enforces the same access control as the platform — agents can only read resources within the authenticated user's project scope.

This removes the context-switching cost of debugging infrastructure from an IDE: the agent already knows what is deployed, what failed, and what changed — and can act on that knowledge directly.

A Model Context Protocol server that exposes Blazing infrastructure state to external coding agents — enabling tools like Claude Code, Cursor, and Copilot to query deployments, logs, and cluster status directly from the IDE.