Teamcity MCP Server
JetBrains TeamCity CI/CD operations exposed for AI-powered development assistance.
Data last scanned today · Reviewed today
Overview
The TeamCity MCP Server bridges AI coding assistants with JetBrains TeamCity, allowing users to trigger builds, monitor status, and inspect logs directly within their IDE environment. It supports two operational modes: Dev Mode for standard monitoring and build triggering, and Full Mode for extensive infrastructure management, including VCS root configuration and server-wide CRUD operations for build parameters. Built in TypeScript, the server enables runtime switching between security modes, allowing users to toggle between restricted and elevated tool access without restarting the process. It is designed to expose TeamCity's comprehensive CI/CD pipeline capabilities to LLMs that support the Model Context Protocol.
Our verdict
This server carries a high-risk profile (58/100) primarily because it is a community-maintained project rather than an official JetBrains product, and it lacks an editorial security review. While it offers a read-only configuration option to mitigate exposure, users should exercise caution given the absence of OAuth support for authentication. It is recommended primarily for users who require deeper CI/CD integration than official tooling provides and are prepared to manage security best-effort, as the project is in a stable, maintenance-only state.
- Supports runtime mode switching between Dev and Full configurations
- Provides access to 87 tools in Full mode
- Small dependency surface with only seven direct dependencies
- Includes a clear tool matrix documentation for operational safety
- No official JetBrains vendor maintenance or verified security audit
- Lacks OAuth support for secure authentication flows
- Project is in maintenance-only mode with slow issue responsiveness
Setup
{
"mcpServers": {
"teamcity-mcp": {
"args": [
"-y",
"@daghis/teamcity-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| ping | Test MCP server connectivity | low |
| list_projects | List TeamCity projects (paginated) | low |
| get_project | Get project details | low |
| create_project | Create a new project | medium |
| delete_project | Delete a project | high |
| update_project_settings | Update project fields | medium |
| list_project_hierarchy | Parent/child tree (limited depth) | low |
| list_builds | List builds (paginated) | low |
| get_build | Get build details | low |
| trigger_build | Trigger a build | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the system requirements for running this server?
You need Node.js version 20.10.0 or higher, TeamCity Server 2020.1 or later with REST API access, and a valid TeamCity authentication token.
›What is the difference between Dev Mode and Full Mode?
Dev Mode includes 31 tools for safe operations like triggering builds and checking status, while Full Mode provides 87 tools covering advanced tasks like infrastructure management and server administration.
›Can I switch operational modes without restarting the server?
Yes, if you are using version 2.1.0 or later, you can switch between Dev and Full modes at runtime using the get_mcp_mode and set_mcp_mode tools.
›How does this compare to official TeamCity AI integrations?
JetBrains provides first-party AI integration and CLI tools which are the recommended default; this project is primarily useful for specific write and management operations not currently covered by those official tools.
›Is this project currently under active development?
No, as of June 2026, the project is in stable, low-key maintenance mode, meaning future security fixes are provided on a best-effort basis.
Badge
Maintain this server? Add the live badge to your README.