MCP Directory

TeamCity MCP Server

Control JetBrains TeamCity CI/CD — builds, tests, agents, and configs — from AI coding assistants.

Unverified
stdio (local)
API key
TypeScript

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run
npx -y @daghis/teamcity-mcp

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "teamcity-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@daghis/teamcity-mcp"
      ],
      "env": {
        "TEAMCITY_URL": "https://teamcity.example.com",
        "TEAMCITY_TOKEN": "tc_<your_token>",
        "MCP_MODE": "dev"
      }
    }
  }
}

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

  • Node.js >= 20.10.0 (LTS 20, 22, 24 tested in CI)
  • TeamCity Server 2020.1+ with REST API access
  • A TeamCity authentication token

About TeamCity MCP Server

The TeamCity MCP Server lets developers using AI-powered coding assistants interact with a JetBrains TeamCity server directly from their development environment via MCP tools. It exposes TeamCity operations — triggering and monitoring builds, fetching logs, inspecting test failures, and (in Full mode) managing build configurations, steps, triggers, VCS roots, agents, parameters, and the build queue — as typed MCP tools. It uses a singleton API client over an auto-generated OpenAPI TeamCity client, supports two operational modes (Dev/Full) with runtime switching, and works with TeamCity Server 2020.1+. It positions itself as a power-tool complement to TeamCity 2026.1's built-in MCP endpoint, adding write operations, multi-server support, pre-2026.1 compatibility, and a larger typed tool surface.

Tools & capabilities (16)

TriggerBuild

Queue a new build.

GetBuildStatus

Check build progress.

FetchBuildLog

Retrieve build logs.

ListBuilds

Search builds by criteria.

ListTestFailures

Get failing tests.

GetTestDetails

Detailed test information.

AnalyzeBuildProblems

Identify failure reasons.

create_build_config

Create new TeamCity build configurations with full support for VCS roots (Git, SVN, Perforce), build steps (script, Maven, Gradle, npm, Docker, PowerShell), triggers, and parameters. Full mode only.

clone_build_config

Duplicate existing configurations into any project, preserving steps, triggers, and parameters. Full mode only.

update_build_config

Adjust names, descriptions, artifact rules, and pause state for a configuration. Full mode only.

manage_build_steps

Add, update, remove, or reorder build steps through a single tool surface. Full mode only.

manage_build_triggers

Add or delete build triggers with full property support. Full mode only.

create_vcs_root

Define a VCS root. Full mode only.

add_vcs_root_to_build

Attach a VCS root to a build configuration. Full mode only.

get_mcp_mode

Report the current operational mode (dev or full).

set_mcp_mode

Switch the operational mode at runtime without a restart (v2.1.0+).

When to use it

  • Trigger a build on a feature branch and monitor its status from your AI assistant
  • Investigate why a build's tests failed by fetching logs and analyzing build problems
  • Deploy a staging environment with the latest build
  • Create or clone TeamCity build configurations, including VCS roots, build steps, and triggers (Full mode)
  • Manage parameters, agents, the build queue, and mutes across one or more TeamCity servers (Full mode)

Security notes

Token-based authentication only (no username/password); use a token with minimal required permissions — read-only tokens work for most Dev mode operations. Logs redact sensitive values including tokens. Prefer Dev mode unless Full mode is explicitly needed, since Full mode enables destructive operations (project deletion, agent management). AI assistants can be manipulated via prompt injection embedded in build logs or test output; Dev mode's limited tool set reduces the blast radius. All actions appear in TeamCity's audit log under the token's user. Always use HTTPS for TeamCity connections.

TeamCity MCP Server FAQ

How do I add it to Claude Code?

Run `claude mcp add teamcity -- npx -y @daghis/teamcity-mcp` (relying on a .env file), or pass env vars inline with `-e TEAMCITY_URL=... -e TEAMCITY_TOKEN=...`. Add `-s user` to install user-wide instead of project-scoped.

What is the difference between Dev mode and Full mode?

Dev mode (default) exposes 31 safe CI/CD tools (~14k context tokens) for triggering/monitoring builds and reading data. Full mode exposes all 87 tools (~26k tokens), adding build-config CRUD, VCS/agent management, parameter CRUD, queue management, and server administration. Set MCP_MODE=full, or switch at runtime with set_mcp_mode (v2.1.0+).

Does it work with older TeamCity servers?

Yes. It supports TeamCity Server 2020.1+ with REST API access, and is a recommended option for servers older than 2026.1 (which ships a more limited built-in MCP endpoint).

How does authentication work?

Token-based only — set TEAMCITY_TOKEN via an environment variable or config file. Username/password is not supported. A read-only token works for most Dev mode operations, and tokens are redacted in logs.

Any tips for Windows?

Claude Code on Windows may not merge env vars correctly, so pass configuration via CLI arguments (e.g. `--url`, `--token`) or a `--config` file path in the args array instead of the env block.

Alternatives to TeamCity MCP Server

Compare all alternatives →

GitHub's official server for repos, issues, PRs, and Actions — local Docker or hosted remote.

Featured
Verified
stdio (local)
API key
Go
7 tools
Updated 15 days agoRepo

Official AWS Labs server that lets agents call any AWS API via the AWS CLI surface.

Verified
stdio (local)
API key
Python
3 tools
Updated 17 days agoRepo

Bulk Kubernetes port forwarding with an MCP server that lets AI assistants forward services, inspect pods, and monitor traffic.

Unverified
stdio (local)
No auth
Go
28 tools
Updated 9 days agoRepo