CI Monitor MCP Server

An MCP server that lets agents list Buildkite builds and read failed-job logs, backed by the connection set up in CI Monitor.

packages/ci-monitor-mcp

This package is both an MCP server and a small Electron console window for watching its calls. Agents use the tools to check CI without opening Buildkite.

Tools and resources

Tool	Returns
robos_ci_list_runs	The 30 most recent builds (optionally filtered by status or branch). Run IDs look like buildkite:organization:pipeline:number.
robos_ci_get_status	The latest build on an exact branch name, or null.
robos_ci_get_logs	The failed-job logs for a run ID from robos_ci_list_runs.
robos_ci_get_failures	Failed jobs, commit, log excerpt and artifact link for a run ID.
robos_ci_retry_run	Always an error. The integration is read-only; retry in Buildkite.
robos_ci_get_deployments	An empty list. Deployments are not tracked.

Resources: robos://ci-monitor-mcp/ci/current and robos://ci-monitor-mcp/ci/deployments/latest.

Buildkite connection

The server uses the Buildkite connection saved in CI Monitor (~/.config/robos/ci-providers.json), which points to a token in pass. If no connection exists, the tools fail with “Configure Buildkite in CI Monitor before using CI tools.” Token and network errors are returned as errors; the live service never invents sample data.

The console window

The window has Inspect Failed Tests and Retry Failed Pipeline buttons, counters (runs, pass rate, tools, deployments), a runs table, a log pane and a Live CI MCP Protocol Trace with Clear Trace. It calls the same service over Electron IPC.

Demo mode

createCIMonitorMCPServer({ demo: true }) (or passing runsFile) swaps in a sample service with two fake runs stored in ~/.config/robos/ci/runs.json, where a retry flips a failed run to passed. This exists for the repository’s tests and demos; the app itself starts the live service.

Registration

When the server is created it records its tool and resource names in ~/.config/robos/mcp/servers.json. It opens no port unless a port option is passed. The robos-mcp-router reads that registry. Run the window with electron packages/ci-monitor-mcp; npm test there runs node --test.

Source: packages/ci-monitor-mcp.

More in Agent Services & MCP Servers

Agent Autoconfig Writes MCP configuration and instruction files so Claude Code, Gemini, Copilot and Cursor all point at the RobOS MCP router. Agent Daemon (agentd) Keeps a registry of sub-agent sessions, each with its own home directory and environment, behind a Unix socket and a small window. Agent Profile Daemon Creates short-lived agent profiles with their own home directory (tmpfs when run as root) and runs commands with that home and environment. Agent Session Library Node.js client for the agentd socket, plus a small demo window and a simulated test-driven-development runner. Dev Tools MCP Server An MCP server with a small catalog of developer CLI tools; "install" and "check" read and write a JSON file and do not touch the system. Engineering Knowledge Graph MCP Server An MCP server that lets agents search and edit a small node store, query and propose changes to the SDLC graph, and look up schema types. IDE Bridge MCP Server An MCP server that forwards IDE commands (open file, breakpoints, run configurations, refactorings) to the RobOS IntelliJ plugin on port 63343. MCP Router Single MCP endpoint that lists the tools of the servers in the registry and routes tool calls to them, with built-in fallbacks. MCP Server Framework Node.js library for building small Model Context Protocol servers, with an HTTP and a stdio transport and a shared registry file. RobOS CLI Tools Four shell scripts for scripts and agents: send a notification, set the active task, append to the work journal, and emit or read events. System MCP Server MCP server with six tools for preferences, notifications, a tool inventory, file-name search and the active task, backed by a JSON file with sample data. Task Manager MCP Server MCP server with seven tools for listing, creating and advancing tasks stored in ~/.config/robos/tasks/tasks.json. Workspace Manager MCP Server MCP server with six workspace tools, backed by a JSON file of sample workspaces. Several tools return canned results and do not run anything.