# TeamCity MCP Server

A Model Context Protocol server that bridges AI coding assistants such as Claude Code, Cursor and Windsurf with a JetBrains TeamCity server, exposing build triggers, logs, test failures and configuration management as MCP tools.

TeamCity MCP Server is an MCP server that exposes JetBrains TeamCity CI/CD operations as MCP tools, so AI coding assistants such as Claude Code, Cursor and Windsurf can trigger builds, monitor status, fetch build logs, inspect test failures, and manage TeamCity configuration directly from the development environment. It authenticates to TeamCity with a token and redacts sensitive values from its logs.

It runs in one of two modes: a default Dev mode with 31 tools for safe CI/CD operations such as triggering builds, reading parameters and investigating problems, and a Full mode with 87 tools that adds complete infrastructure management, including creating and cloning build configurations, managing build steps, triggers and dependencies, configuring VCS roots and agents, full CRUD for parameters, and queue and server administration; the two modes can be switched at runtime without restarting the server.

The project describes itself, as of June 2026, as stable but in low-key maintenance, since JetBrains has since shipped its own official MCP and CLI integration for TeamCity, which this project's documentation recommends as the better default for most workflows going forward. It is written in TypeScript and MIT licensed.

Website: https://github.com/Daghis/teamcity-mcp