Teamcity MCP vs MCP Server Kubernetes
A side-by-side look at the Teamcity MCP and MCP Server Kubernetes MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Teamcity MCP for cloud platforms work as a local process; choose MCP Server Kubernetes for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Teamcity MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TEAMCITY_URL, TEAMCITY_TOKEN. - You want tools like
pageSize, maxPages, all.
Choose MCP Server Kubernetes when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 67/100 · Great | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | TEAMCITY_URLTEAMCITY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 31 | 1,607 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Teamcity MCP | View MCP Server Kubernetes |
Tools & capabilities
Teamcity MCP tools 5
pageSizemaxPagesallcountlist_builds
MCP Server Kubernetes tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Teamcity MCP
{
"mcpServers": {
"daghis-teamcity-mcp": {
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp"
],
"env": {
"TEAMCITY_URL": "YOUR_TEAMCITY_URL_HERE",
"TEAMCITY_TOKEN": "YOUR_TEAMCITY_TOKEN_HERE"
}
}
}
}
MCP Server Kubernetes
{
"mcpServers": {
"flux159-mcp-server-kubernetes": {
"command": "npx",
"args": [
"-y",
"mcp-server-kubernetes"
]
}
}
}
Frequently asked questions
Teamcity MCP is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Server Kubernetes belongs to Cloud Platforms and uses a local stdio subprocess. Pick Teamcity MCP for cloud platforms work and MCP Server Kubernetes for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Teamcity MCP is listed as free. Auth: api key required. MCP Server Kubernetes has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add daghis-teamcity-mcp and flux159-mcp-server-kubernetes as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Teamcity MCP has a quality signal of 67/100 (Great) with 4 views, 0 installs and 31 GitHub stars. MCP Server Kubernetes has 48/100 (Fair) with 0 views, 0 installs and 1,607 GitHub stars.