analyze_build_problems
Analyze and report build problems and failures.
LABSCO SUMMARY
It covers the whole loop around a build — trigger, wait, read the log, find the failing test — without leaving the conversation.
Decide the mode first: dev is the default and stays on the read-and-run side, while full opens up creating and editing build configurations, steps, triggers and parameters. The author now describes the project as stable and in low-key maintenance and points at JetBrains' own built-in TeamCity MCP for read-and-rerun work, so the case for this one rests on that write surface.
What it is
An MCP server over TeamCity's REST API. It connects to your own TeamCity server with a personal access token, and keeps the write operations behind a mode switch so the default surface is read-and-run only.
What you get
- A build end to end: trigger one on a branch with a comment and properties, wait until it reaches a terminal state, then read status and detailed results
- Build logs with line-based paging — fetch a page, tail a fixed number of lines, or write the log straight to a path
- Failure triage: list the failing tests for a build, open one test's details, and pull build problems and their occurrences
- Artifacts: list what a build produced, browse into subdirectories, and download one or many as base64, text or a stream
- The project side: projects and their hierarchy, build configurations, branches, parameters, VCS changes, the queue, open investigations and muted tests
- Cancelling work: drop a queued build, or stop a running one and optionally put it back in the queue
- Set MCP_MODE to full and the write surface appears — create_project, clone_build_config, manage_build_steps, manage_build_triggers, add_parameter and the rest — with get_mcp_mode and set_mcp_mode switching modes without a restart
Requirements
Node.js >= 20.10.0 and a TeamCity Server 2020.1+ with REST API access. Two required environment variables: TEAMCITY_URL for the server and TEAMCITY_TOKEN for a personal access token. MCP_MODE selects the tool surface — dev by default, full for the write operations. Runs over stdio, launched with npx -y @daghis/teamcity-mcp.
Setup effort
One command plus a key — npx -y @daghis/teamcity-mcp, then supply credentials
USE CASES
01
Working out why the nightly build went red
List the failing tests for the build, open the ones that matter, and read the recorded build problems.
02
Running a build on your branch and waiting for it
Trigger the configuration on a branch, block until it finishes, then read the detailed result.
03
Reading a long build log without drowning in it
Fetch the log a page at a time, or tail a fixed number of lines from the end.
04
Getting a build's artifacts onto your disk
List what the build produced, browse into subdirectories, then download the files you want.
05
Clearing a jammed build queue
See what is waiting, drop the builds that should not run, and stop a running one with a comment.
06
Turning on the write tools for a pipeline change
Check which mode the server is in, then switch to full so build-config and parameter editing appear.
32 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
cancel_build
Cancel or stop a running or queued build, with optional comment and requeue flag. Returns the cancelled build; returns 404 if the build is unknown.
cancel_queued_build
Cancel a queued (not-yet-running) build. Idempotent; returns 404 if the build already started or was cancelled.
download_build_artifact
Download a single build artifact, with base64, text, or streaming output. Returns the artifact bytes or stream metadata; returns 404 if the build or path is unknown.
download_build_artifacts
Download multiple build artifacts, with base64, text, or streaming output. Returns per-artifact payloads or stream metadata; returns 404 if the build or any path is unknown.
fetch_build_log
Fetch a build log. Supports line-based pagination and streaming output.
get_build
Get details of a specific build. Works for queued, running, and finished builds.
get_build_config
Get details of a build configuration.
get_build_results
Get detailed results of a build. Optionally includes tests, artifacts, changes, statistics, and dependencies.
get_build_status
Get build status. Optionally includes test and problem summaries plus queue context.
get_mcp_mode
Get the current MCP mode. Dev mode is read-only; full mode enables all operations.
get_project
Get details of a specific project.
get_server_info
Get TeamCity server info including version, build number, and state.
get_test_details
Get detailed information about test failures.
list_branches
List branches for a project or build configuration.
list_build_artifacts
List artifact files and directories for a build, optionally browsing into subdirectories. Returns an array of artifact entries with name, path, size, and isDirectory flag.
list_build_configs
List build configurations. Supports pagination and locator filtering.
list_builds
List TeamCity builds. Supports pagination and locator filtering.
list_changes
List VCS changes. Supports pagination.
list_investigations
List open investigations. Supports pagination.
list_muted_tests
List muted tests. Supports pagination.
list_parameters
List parameters for a build configuration.
list_problem_occurrences
List build problem occurrences. Supports pagination.
list_problems
List build problems. Supports pagination.
list_project_hierarchy
List project hierarchy showing parent-child relationships.
list_projects
List TeamCity projects. Supports pagination and locator filtering.
list_queued_builds
List queued builds. Supports TeamCity queue locator filtering and pagination.
list_test_failures
List test failures for a build. Supports pagination.
ping
Test MCP server connectivity. Returns a confirmation echo and optional message.
set_mcp_mode
Switch MCP mode at runtime. Returns previous and current modes with the updated tool count; idempotent and notifies clients of the list change.
trigger_build
Trigger a new build; runs asynchronously, use wait_for_build to monitor. Returns the queued build id; returns 404 if buildTypeId is unknown.
wait_for_build
Wait for a build to reach a terminal state (finished, canceled, failed). Long-running; polls until completion or timeout.
BEFORE YOU INSTALL
What to know first
Tools you get
32 tools when we connected; the project documents 90.
Requires
- npx on PATH
- Node.js >= 20.10.0
- TEAMCITY_TOKEN in your environment
Where it runs
All 5 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @daghis/teamcity-mcpMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add teamcity -- npx -y @daghis/teamcity-mcpClaude Code — env vars
CLAUDE CODE — ENV VARS · TERMINAL
claude mcp add teamcity -e TEAMCITY_URL="<YOUR_TEAMCITY_URL>" -e TEAMCITY_TOKEN="tc_<<YOUR_TOKEN>>" -- npx -y @daghis/teamcity-mcpClaude Code — arguments
CLAUDE CODE — ARGUMENTS · TERMINAL
claude mcp add teamcity -- npx -y @daghis/teamcity-mcp --url "<YOUR_TEAMCITY_URL>" --token "tc_<<YOUR_TOKEN>>" --mode devAny MCP client — Windows arguments
ANY MCP CLIENT — WINDOWS ARGUMENTS · JSON
{
"mcpServers": {
"teamcity": {
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp",
"--url",
"<YOUR_TEAMCITY_URL>",
"--token",
"<YOUR_TOKEN>"
]
}
}
}Any MCP client — Windows config file
ANY MCP CLIENT — WINDOWS CONFIG FILE · JSON
{
"mcpServers": {
"teamcity": {
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp",
"--config",
"<YOUR_PATH_TO_TEAMCITY>"
]
}
}
}
