You can run a dedicated MCP server that bridges AI coding assistants with JetBrains TeamCity, exposing TeamCity operations as MCP tools. This lets you trigger builds, fetch logs, inspect failures, and manage configurations directly from your AI tooling or development environment.

How to use

Connect your MCP client to the TeamCity MCP Server to start issuing commands that control TeamCity from your AI-powered workflows. You can run in development mode for safe, limited tool access or switch to full mode for complete infrastructure management. Use the available tools to trigger builds, monitor progress, fetch logs, examine test failures, and read or modify configurations and parameters as needed. If you prefer runtime flexibility, you can switch modes at runtime with compatible MCP clients that support notifications.

How to install

Prerequisites: ensure you have Node.js version 20.x or newer installed on your system. You also need access to a TeamCity Server (2020.1+ is supported) and a TeamCity authentication token.

# Quick start from source
# 1) Clone the repository
git clone https://github.com/Daghis/teamcity-mcp.git
cd teamcity-mcp

# 2) Install dependencies
npm install

# 3) Configure environment
cp .env.example .env
# Edit .env with your TeamCity URL and token

# 4) Run in development mode
npm run dev

Configuration and usage notes

You configure the server with environment variables. Common options include the TeamCity URL, the authentication token, and the MCP mode. The server exposes an MCP API surface with tools that map to TeamCity REST endpoints. Use a local environment file or set variables inline when starting the server.

Configuration and usage details

Environment variables (example keys): PORT=3000 NODE_ENV=development LOG_LEVEL=info TEAMCITY_URL=https://teamcity.example.com TEAMCITY_TOKEN=your-auth-token

Optional aliases:

TEAMCITY_SERVER_URL=...

TEAMCITY_API_TOKEN=...

MCP_MODE=dev

Optional advanced TeamCity options (defaults shown)

CONNECTION: TEAMCITY_TIMEOUT=30000

TEAMCITY_MAX_CONCURRENT=10

TEAMCITY_KEEP_ALIVE=true

TEAMCITY_COMPRESSION=true

Retry, Pagination, and Circuit Breaker settings can be added as needed

Examples and tips

Examples of common actions you can perform through the MCP interface include building trigger requests, status checks, and log retrievals. Use the MCP tools to create, clone, or update build configurations in Full mode, manage build steps, triggers, VCS roots, and parameters, and handle queue management and server administration.

Available tools

TriggerBuild

Queue a new build for a given build configuration and project, returning the new build identifier.

GetBuildStatus

Check progress and current status of a running or completed build.

FetchBuildLog

Retrieve the logs for a specific build to diagnose failures or verify output.

ListBuilds

Search and list builds by criteria such as project, configuration, or status.

ListTestFailures

Get a list of failing tests for a build or configuration.

GetTestDetails

Provide detailed information about a specific test case, including stack traces and messages.

AnalyzeBuildProblems

Identify failure reasons based on build logs and test results.

create_build_config

Create a new TeamCity build configuration with support for VCS roots, steps, triggers, and parameters.

clone_build_config

Duplicate an existing build configuration within a project, preserving steps, triggers, and parameters.

update_build_config

Modify build configuration properties such as name, description, artifact rules, and pause state.

manage_build_steps

Add, update, remove, or reorder build steps in a configuration.

manage_build_triggers

Add or delete build triggers with full property support.

create_vcs_root

Define a VCS root for a project or configuration.

add_vcs_root_to_build

Attach a VCS root to a specific build configuration.