MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-daghis-teamcity": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Control Protocol (MCP) server that bridges AI coding assistants with JetBrains TeamCity CI/CD server, exposing TeamCity operations as MCP tools.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
Enhanced MCP server for GitLab: group projects listing and activity tracking
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for io.github.Daghis/teamcity and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Control Protocol (MCP) server that bridges AI coding assistants with JetBrains TeamCity CI/CD server, exposing TeamCity operations as MCP tools.
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=fullor use runtime mode switching (v2.1.0+). See CHANGELOG.md for details.
Dev Mode (default): Safe CI/CD operations (31 tools, ~14k context tokens)
Full Mode: Complete infrastructure management (87 tools, ~26k context tokens)
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.
TeamCity 2026.1 ships with a built-in MCP endpoint at <server-url>/app/mcp exposing three tools: build log retrieval, a generic REST GET, and a build trigger (forced to personal=true). It is server-resident, requires no install, and is a sensible default for read-and-rerun workflows.
teamcity-mcp is a different shape: an 87-tool typed surface focused on AI-driven workflows that need writes, multi-server support, or pre-2026.1 compatibility.
| Use case | Recommendation |
|---|---|
| Read build logs, trigger builds, simple read flows | Built-in (TeamCity 2026.1+) — zero install |
| Manage parameters, agents, queue, mutes, build configs, VCS roots | teamcity-mcp |
| TeamCity server older than 2026.1 |