Log inSubmit server
Teamcity MCP logo

Teamcity MCP

by Daghis

Connects AI coding assistants to TeamCity for build, test, agent, and CI/CD pipeline operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Teamcity MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "daghis-teamcity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@daghis/teamcity-mcp"
      ],
      "env": {
        "TEAMCITY_URL": "YOUR_VALUE_HERE",
        "TEAMCITY_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @daghis/teamcity-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 24d ago.

Overview

Daghis/teamcity-mcp MCP server connects AI coding assistants to a JetBrains TeamCity server through MCP tools. It supports a default dev mode for build and test workflows and a full mode with broader configuration, queue, agent, and administration operations. Use it when an assistant needs to inspect or manage TeamCity through its REST API, provided you can supply a TeamCity URL, token, and Node.js runtime.

Use cases

  • Trigger and monitor TeamCity builds
  • Investigate failed tests and build logs
  • List TeamCity projects and queued builds
  • Create and configure build pipelines
  • Manage TeamCity agents and parameters

Key features

  • Dev and full operational modes
  • Runtime mode switching
  • TeamCity token authentication
  • Build, test, and log operations
  • Full-mode pipeline and infrastructure management
  • Pagination and retry configuration

Tools5

What Teamcity MCP lets your agent do. Expand a tool for its parameters.

Self-reported~9 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

19/19 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @daghis/teamcity-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars31Stargazers on the source repository.
npm downloads5.3kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed5Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Teamcity MCP works

What Daghis/teamcity-mcp does

Daghis/teamcity-mcp MCP server exposes JetBrains TeamCity operations to MCP-compatible coding assistants. It is intended for teams that want an assistant to work with builds, tests, agents, and CI/CD pipeline configuration from the development environment rather than switching to TeamCity for every operation.

The project supports two operating modes. Dev mode is the default and focuses on safer CI/CD tasks, including triggering builds, checking build status, reading logs, investigating test failures, and listing TeamCity projects, configurations, and queued work. Full mode adds infrastructure-oriented operations such as creating or cloning build configurations, managing build steps and triggers, configuring VCS roots and agents, changing parameters, managing the queue, and performing server administration.

How it works

Daghis/teamcity-mcp MCP server runs as a Node.js process and communicates with TeamCity through its REST API. TeamCity authentication uses a token, and the implementation redacts sensitive values in logs. The server uses MCP tools to make TeamCity actions available to the connected assistant.

The repository describes 87 tools in full mode and 31 in dev mode. The exposed interface includes pagination-related entries such as pageSize, maxPages, all, and count, along with list_builds. Tool availability depends on the selected mode. From version 2.1.0 onward, clients can switch modes at runtime with get_mcp_mode and set_mcp_mode; clients that support notifications can receive the updated tool list without restarting.

Setup and configuration

Daghis/teamcity-mcp MCP server requires Node.js 20.10.0 or newer and a TeamCity Server version 2020.1 or later with REST API access. Set TEAMCITY_URL and TEAMCITY_TOKEN, either in a .env file or in the process environment. TEAMCITY_SERVER_URL and TEAMCITY_API_TOKEN are supported aliases.

You can run the package with npx -y @daghis/teamcity-mcp, or clone the repository, install dependencies with npm install, and start the development command with npm run dev. Set MCP_MODE=dev for the default restricted tool set or MCP_MODE=full for all available operations. The server also accepts command-line URL, token, mode, and configuration-file options; the README specifically recommends command-line arguments as a Windows workaround for environment-variable merging issues in Claude Code.

Optional settings cover the listening port, log level, request timeout, concurrency, retries, pagination, compression, keep-alive behavior, circuit breaking, and extra TeamCity request headers. Extra headers can help when TeamCity is behind a reverse proxy that requires additional authentication headers.

Tools and capabilities

  • Trigger and monitor builds.
  • Retrieve build logs and inspect test failures.
  • List projects, build configurations, and queue entries.
  • Create or clone build configurations in full mode.
  • Manage build steps, triggers, dependencies, VCS roots, agents, and parameters in full mode.
  • Manage queue operations and server administration in full mode.

Limitations and notes

The repository labels the project as stable and under low-key maintenance, so issue and pull-request responses may be delayed and security fixes are best-effort. JetBrains now provides its own TeamCity AI integration and TeamCity CLI, which the README identifies as the preferred default for many workflows. Daghis/teamcity-mcp remains relevant when its broader MCP-based write and management operations fit the use case.

Full mode exposes substantially more tools and therefore uses more context: the README estimates about 14,000 tokens for dev mode and 26,000 for full mode. Review the required permissions and management actions before enabling full mode against a production TeamCity instance.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Teamcity MCP

Daghis/teamcity-mcp is an MCP server that connects AI coding assistants to JetBrains TeamCity through its REST API. Its main tools support build and test workflows, logs, projects, configurations, queues, agents, and pipeline administration, with broader operations available in full mode.

Install it with Node.js 20.10.0 or newer by running `npx -y @daghis/teamcity-mcp`, or clone the repository, run `npm install`, and start it with `npm run dev`. Configure the TeamCity URL and token through environment variables, a `.env` file, or supported command-line options.

Set `MCP_MODE=full` before starting the server. Full mode exposes the complete 87-tool set, including build configuration, trigger, agent, parameter, queue, and server administration operations. You can also switch modes at runtime with the `get_mcp_mode` and `set_mcp_mode` tools.

Yes, the README names Cursor as a supported AI coding assistant, along with Claude Code and Windsurf. Connect the MCP process to the client and provide the TeamCity URL and authentication token through environment variables or command-line configuration.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTeamcity MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/daghis-teamcity-mcp?style=directory)](https://allmcps.com/mcp/daghis-teamcity-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/daghis-teamcity-mcp"><img src="https://allmcps.com/api/badge/daghis-teamcity-mcp?style=directory" alt="Teamcity MCP on AllMCPs" /></a>