teamcity — Claude Code MCP server: what it does, how to install
Connects coding assistants to JetBrains TeamCity to launch builds, inspect test failures, and inspect logs directly in chat.
claude mcp add --env TEAMCITY_URL=<TEAMCITY_URL> --env TEAMCITY_TOKEN=<TEAMCITY_TOKEN> --env MCP_MODE=<MCP_MODE> --transport stdio teamcity -- npx -y @daghis/teamcity-mcpWhat teamcity does
This server connects an AI coding assistant to a JetBrains TeamCity instance over the Model Context Protocol. It allows an agent to trigger pipelines, inspect failing tests, and pull build output into the conversation. Tokens stay hidden in log output.
Two modes govern tool availability: Dev and Full. Dev mode enables 31 tools focused on reading queues, checking parameters, and triggering routine runs. Full mode expands the registry to 87 tools, adding build configuration cloning, VCS root changes, and parameter management. Assistants switch modes on the fly using get_mcp_mode and set_mcp_mode.
Running the package requires Node.js 20.10.0 or later alongside TeamCity 2020.1 or newer. Without valid credentials passed through TEAMCITY_URL and TEAMCITY_TOKEN, the connection fails immediately.
What it helps with
- trigger TeamCity builds and track execution progress
- retrieve error logs from failed test runs
- clone build configurations and edit build parameters
- inspect the active build queue and agent status
Example prompts for the agent
- Inspect the latest failed build in TeamCity and pinpoint why the tests failed
- Switch to Full mode with
set_mcp_modeand display the current build queue - Trigger a build for the main test configuration and monitor its progress
How to install teamcity
Platform CLI
claude mcp add --env TEAMCITY_URL=<TEAMCITY_URL> --env TEAMCITY_TOKEN=<TEAMCITY_TOKEN> --env MCP_MODE=<MCP_MODE> --transport stdio teamcity -- npx -y @daghis/teamcity-mcpReplace <…> with your own values
Platform CLI
codex mcp add teamcity --env TEAMCITY_URL=<TEAMCITY_URL> --env TEAMCITY_TOKEN=<TEAMCITY_TOKEN> --env MCP_MODE=<MCP_MODE> -- npx -y @daghis/teamcity-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"teamcity": {
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp"
],
"env": {
"TEAMCITY_URL": "<TEAMCITY_URL>",
"TEAMCITY_TOKEN": "<TEAMCITY_TOKEN>",
"MCP_MODE": "<MCP_MODE>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"teamcity": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp"
],
"env": {
"TEAMCITY_URL": "<TEAMCITY_URL>",
"TEAMCITY_TOKEN": "<TEAMCITY_TOKEN>",
"MCP_MODE": "<MCP_MODE>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e TEAMCITY_URL=<TEAMCITY_URL> -e TEAMCITY_TOKEN=<TEAMCITY_TOKEN> -e MCP_MODE=<MCP_MODE> teamcity npx -y @daghis/teamcity-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about teamcity
How do I install teamcity in Claude Code?
Run claude mcp add teamcity -e TEAMCITY_URL=<TEAMCITY_URL> -e TEAMCITY_TOKEN=<TEAMCITY_TOKEN> -- npx -y @daghis/teamcity-mcp. Replace the placeholders with your server endpoint and API token.
What does teamcity do?
It exposes JetBrains TeamCity actions as MCP tools for coding assistants. The assistant can start builds, read logs, check queue items, and update project settings.
What is the difference between Dev and Full mode?
Dev mode provides 31 safe tools for daily monitoring and running builds. Full mode unlocks 87 tools for structural administration, including VCS roots and build steps.
