A read-only MCP server for TeamCity
Most build questions arrive the same way: someone sends a link to a red build and asks what broke. Answering it by hand means opening the build, scrolling a log that can run to tens of thousands of lines, checking which tests failed and whether they were already muted, and looking at what changed since the last green run. With the read-only MCP server for TeamCity , released as 1.0.0 on November…
The read-only MCP server for TeamCity, released on November 2 as version 1.0.0, simplifies the process of diagnosing failed builds. Users can paste a link to a problematic build, and the server generates a root-cause analysis containing essential information like error lines from the log, failed tests, and commits included in the build. This tool eliminates the need to manually scroll through extensive logs, which can sometimes span tens of thousands of lines.
The server operates on 29 tools across projects, build configurations, builds, logs, tests, agents, and the queue. It is designed to be read-only, ensuring it cannot perform actions like triggering, canceling, pinning, or tagging builds. To set this up, create a read-only token in TeamCity with the necessary permissions limited to project-level access.
The server excels at quickly providing answers to common questions such as "Why did this build fail?" or "Show me the last 10 builds of the API build and which ones failed." It can also list currently offline agents, examine the build queue, and identify who is currently investigating specific failures. Although it does not handle questions related to the timeline of issues, it effectively addresses a wide range of build-related inquiries.
For more details, including the full list of tools and a comparison with JetBrains' MCP server and community versions, visit the repository on GitHub at readonly-mcp-teamcity.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
