Dev Tools & GitMCP RegistrynpmA · 84

teamcity MCP server

Name: teamcity
Author: Daghis

io.github.Daghis · Updated today

MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants

At a glance

teamcity is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y @daghis/teamcity-mcp`, and needs TEAMCITY_URL and TEAMCITY_TOKEN. It scores A (84/100) on the MCP Skills Hub health score as of Oct 27, 2026.

Source 31

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install teamcity in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install teamcity in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add teamcity -e 'TEAMCITY_URL=<TEAMCITY_URL>' -e 'TEAMCITY_TOKEN=<TEAMCITY_TOKEN>' -- npx -y @daghis/teamcity-mcp

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.
3
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install teamcity in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

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

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install teamcity in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

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

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install teamcity in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.teamcity]
command = "npx"
args = ["-y", "@daghis/teamcity-mcp"]
env = { TEAMCITY_URL = "<TEAMCITY_URL>", TEAMCITY_TOKEN = "<TEAMCITY_TOKEN>" }

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install teamcity in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

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

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install teamcity in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

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

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.

How to install teamcity in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "teamcity": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@daghis/teamcity-mcp"
      ],
      "env": {
        "TEAMCITY_URL": "<TEAMCITY_URL>",
        "TEAMCITY_TOKEN": "<TEAMCITY_TOKEN>"
      }
    }
  }
}

Fill in your credentials
Replace <TEAMCITY_URL>, <TEAMCITY_TOKEN> with your real values. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What does teamcity need from you?

API key — TeamCity personal access token with required permissions

TEAMCITY_URLrequiredEnvironment variable
Base URL of your TeamCity server
TEAMCITY_TOKENrequiredsecretEnvironment variable
TeamCity personal access token with required permissions
MCP_MODEoptionalEnvironment variable
Operational mode: dev (default) or full for elevated administrative tools

Pass secrets through your shell environment rather than committing them into a config file.

What tools does teamcity expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 0 of 0 source files.

No capabilities were observed, but the source could not be fully read — treat this as unknown rather than none.

How it was published

Published by a verified CI identity (github trusted publishing) rather than a personal token.
Has a provenance attestation tying this artifact to the commit it was built from.
1 npm maintainer — a single point of compromise · last published by GitHub Actions.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit today — Actively maintained.
31 GitHub stars — Community adoption signal.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 84

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 0 days ago.
Adoption20%46%
31 stars.
Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
Provenance15%100%
Package and registry entry point at the same repository.
Packaging15%100%
Publishes a pinned version (2.12.11).

Documentation

Full README

TeamCity MCP Server

A Model Control Protocol (MCP) server that bridges AI coding assistants with JetBrains TeamCity CI/CD server, exposing TeamCity operations as MCP tools.

[!NOTE] Project status (October 2026): stable, low-key maintenance. This does what it set out to do and is no longer under active development. It still works and stays installable; issues and PRs may get slow or no response, and security fixes are best-effort. JetBrains now ships official AI integration for TeamCity — an MCP server built into TeamCity 2026.1+ and the TeamCity CLI with an installable agent skill — which is the better default for most workflows. See _How this compares to JetBrains' official tooling_ below before adopting.

Overview

The TeamCity MCP Server allows developers using AI-powered coding assistants (Claude Code, Cursor, Windsurf) to interact with TeamCity directly from their development environment via MCP tools.

Upgrading from 1.x? Version 2.0.0 moved 15 tools from Dev to Full mode, including queue management, agent compatibility checks, and server health monitoring. If you relied on these tools in Dev mode, switch to MCP_MODE=full or use runtime mode switching (v2.1.0+). See CHANGELOG.md for details.

Features

🚀 Two Operational Modes

Dev Mode (default): Safe CI/CD operations (31 tools, ~14k context tokens)
Trigger builds and monitor status
Fetch build logs and inspect test failures
List projects, configurations, and queue
Read parameters and investigate problems

Full Mode: Complete infrastructure management (87 tools, ~26k context tokens)
All Dev mode features, plus:
Create and clone build configurations
Manage build steps, triggers, and dependencies
Configure VCS roots and agents
Full CRUD for parameters (build config, project, and output parameters)
Queue management and server administration

Runtime Mode Switching (v2.1.0+): Switch between modes at runtime using the get_mcp_mode and set_mcp_mode tools—no restart required. MCP clients that support notifications will see the tool list update automatically.

See the Tools Mode Matrix for the complete list of 87 tools and their availability by mode.

🎯 Key Capabilities

Trigger and monitor builds, fetch logs, and inspect test failures
Token-based authentication to TeamCity; sensitive values redacted in logs
Modern architecture: simple, direct implementation with a singleton client
Performance-conscious: fast startup with minimal overhead
Clean codebase with clear module boundaries

Excerpt — the full document is on GitHub.

Alternatives to teamcity

Maintain teamcity? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![teamcity on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-daghis-teamcity)](https://mcp-skills-hub.vercel.app/mcps/io-github-daghis-teamcity)

Catalog data refreshed Oct 27, 2026. Something wrong? Report it.