Developer · Local MCP server
Teamcity
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Daghis/teamcity- Version
- 2.12.8
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- Daghis (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Daghis) · how
- Website
- github.com/Daghis/teamcity-mcp
- Repository
- github.com/Daghis/teamcity-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @daghis/teamcity-mcp | 2.12.8 | stdio |
How to connect Teamcity
Teamcity runs locally from a Node.js package published to the npm registry: @daghis/teamcity-mcp version 2.12.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @daghis/teamcity-mcp@2.12.8. It reads these environment variables: TEAMCITY_URL (required), TEAMCITY_TOKEN (required, secret) and MCP_MODE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"teamcity": {
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp@2.12.8"
],
"env": {
"TEAMCITY_URL": "<value>",
"TEAMCITY_TOKEN": "<secret>",
"MCP_MODE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TatNetDeploy and manage web apps on TatNet, a Russian cloud: builds, logs, env, domains, balance. | Remote · HTTPLive check: sign-in required |
| TaufunctionsServerless functions for coding agents. Deploy, invoke, monitor. 13 tools, stdio or remote. | Remote & Local · HTTP, SSE, stdioLive check: ✓ handshake |
| Tdai Memory MCPLocal-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec. | Local · stdio |
| Tdcv2Deterministic test data from a.tdc config, generated locally by the TDCv2 engine. | Local · stdio |
| TeamMemoryTeam experience database - let AI accumulate, retrieve and apply team knowledge across chats. | Local · stdio |
| TeamSharedShared memory for coding agents. Stop re-explaining your codebase every session. | Remote · HTTPLive check: sign-in required |
| TeamspendCompares AI coding tool spend before and after a migration via MCP tools. | Local · stdio |
| Tech Debt MCPMCP Server for analyzing technical debt across multiple programming languages. | Local · stdio |