# Daghis/teamcity-mcp [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/Daghis/teamcity-mcp  
**GitHub Stars:** 31  
**npm Downloads (last month):** 5305  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/daghis-teamcity-mcp

## Description
MCP server for JetBrains TeamCity with 87 tools for builds, tests, agents, and CI/CD pipeline management. Features dual-mode operation (dev/full) and runtime mode switching.

## Tools
Capabilities this server exposes over MCP:

- **pageSize**
- **maxPages**
- **all**
- **count**
- **list_builds**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "teamcity-mcp": {
    "command": "npx",
    "args": ["-y","@daghis/teamcity-mcp"],
    "env": {
      "TEAMCITY_URL": "",
      "TEAMCITY_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `TEAMCITY_URL`, `TEAMCITY_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/daghis-teamcity-mcp/readme_