BuildMonitor 0.1.0-beta.16

BuildMonitor

A build/CI monitor that runs in the system tray on Windows, macOS and Linux. It polls the CI services a developer cares about, shows one row per pipeline with a progress bar and countdown for running builds, links straight to the build, the branch and the pull request, can retry or cancel a build, and copies the log of a failed one. A local MCP server lets an AI assistant read and act on the same list.

Install

dotnet tool install --global BuildMonitor --prerelease

Run buildmonitor to start the tray app. One install works on every operating system: the package carries a head for each platform and the launcher starts the right one.

The command also takes show, hide, quit, refresh, status and mcp.

To update, use Update in the tray menu, which restarts BuildMonitor on the new version. To update from the command line on Windows, first quit the tray with buildmonitor quit and close any AI assistant using the MCP server, since both hold the installed files:

dotnet tool update --global BuildMonitor --prerelease

An assistant stays on the old version of the MCP server until it connects it again.

Supported services

AppVeyor, Azure DevOps, Bitbucket Pipelines, GitHub Actions, GitLab CI, GoCD, Jenkins, Octopus Deploy, TeamCity and Travis CI.

Each takes a token or API key created in that service's own UI, and GitHub, GitLab and Azure DevOps can also sign in through the browser. Credentials are kept in the platform's secret store: the Windows Data Protection API, the macOS login Keychain, or the Secret Service on Linux. settings.json never holds one.

MCP server

buildmonitor mcp runs a Model Context Protocol server over stdio, so a local AI assistant can read the same builds the tray shows and act on them. For Claude Code:

claude mcp add --transport stdio buildmonitor --scope user -- buildmonitor mcp

The server also ships a triage command for working through every failing build whose repository is checked out under the code directory, on every connection. It reads the logs, groups the failures that share a cause before investigating any of them, and reproduces each from its checkout without switching, stashing or discarding anything there. In Claude Code:

/mcp__buildmonitor__triage

It only diagnoses by default. /mcp__buildmonitor__triage * true has it fix the failures as well, with the changes left uncommitted for review.

See the MCP docs for the other clients, the tools it exposes, and the triage arguments.

Documentation

• Tray
• Options
• Filters
• Authentication
• MCP server
• Linux
• macOS
• Troubleshooting
• Provider APIs

See Milestones for release notes.