Teamcity MCP vs Shipvela

In-depth architectural comparison of the Teamcity MCP and Shipvela MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Teamcity MCP when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: TEAMCITY_URL, TEAMCITY_TOKEN.
• Primary tools included: pageSize, maxPages, all.

Explore Teamcity MCP Details

S

Choose Shipvela when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Freemium).

Explore Shipvela Details

Feature & Specification Comparison

Specification	Teamcity MCP Daghis Cloud Platforms	S Shipvela Cloud Platforms
Summary	MCP server for JetBrains TeamCity with 87 tools for builds, tests, agents, and CI/CD pipeline management. Features dual-mode operation (dev/full) and runtime mode switching.	Shipvela vendor-maintained remote Streamable HTTP MCP at https://shipvela.com/mcp for creating website projects, deploying supported GitHub repositories, and reading operation/deployment status, build logs and usage. Requires a Shipvela account with OAuth S256 PKCE and dynamic client registration; GitHub deployment uses an existing Shipvela GitHub connection. Hobby starts free with 3 projects and 20 publishes/month; paid plans are available. Public beta Codex plugin and publishing skill: https://github.com/stefanautomateed/shipvela-codex. Hosted runtime is private and no source license or authenticated health benchmark is claimed. Maker submission by Stefan Mitrovic with Codex assistance.

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "daghis-teamcity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@daghis/teamcity-mcp"
      ],
      "env": {
        "TEAMCITY_URL": "YOUR_TEAMCITY_URL_HERE",
        "TEAMCITY_TOKEN": "YOUR_TEAMCITY_TOKEN_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "shipvela": {
      "url": "https://shipvela.com/mcp"
    }
  }
}

Related MCP Server Comparisons