Vruum Gtm MCP vs Teamcity MCP
A side-by-side look at the Vruum Gtm MCP and Teamcity MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vruum Gtm MCP for cloud platforms work as a local process; choose Teamcity MCP 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 Vruum Gtm MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VRUUM_MCP_TOKEN, VRUUM_MCP_URL, VRUUM_MCP_TIMEOUT_MS, VRUUM_CONFIG_DIR.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 44/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | VRUUM_MCP_TOKENVRUUM_MCP_URLVRUUM_MCP_TIMEOUT_MSVRUUM_CONFIG_DIR | TEAMCITY_URLTEAMCITY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 31 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Vruum Gtm MCP | View Teamcity MCP |
Tools & capabilities
Vruum Gtm MCP tools
No tool names declared yet. Check the project README from the listing page.
Teamcity MCP tools 5
pageSizemaxPagesallcountlist_builds
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.
Vruum Gtm MCP
{
"mcpServers": {
"mcp-37": {
"command": "npx",
"args": [
"-y",
"@vruum/cli"
],
"env": {
"VRUUM_MCP_TOKEN": "YOUR_VRUUM_MCP_TOKEN_HERE",
"VRUUM_MCP_URL": "YOUR_VRUUM_MCP_URL_HERE",
"VRUUM_MCP_TIMEOUT_MS": "YOUR_VRUUM_MCP_TIMEOUT_MS_HERE",
"VRUUM_CONFIG_DIR": "YOUR_VRUUM_CONFIG_DIR_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
Vruum Gtm MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Teamcity MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Vruum Gtm MCP for cloud platforms work and Teamcity MCP 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.
Vruum Gtm MCP has no declared pricing — check the project's own site. Teamcity MCP is listed as free. Auth: api key required. 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 mcp-37 and daghis-teamcity-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vruum Gtm MCP has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Teamcity MCP has 67/100 (Great) with 4 views, 0 installs and 31 GitHub stars.