teamcity-mcp and mcp-jetbrains
These are **complements** — TeamCity MCP controls CI/CD build pipelines and test execution, while JetBrains IDE MCP provides local development environment integration, allowing developers to view build results and manage CI/CD directly from their IDE during development.
About teamcity-mcp
Daghis/teamcity-mcp
Model Context Protocol (MCP) server for JetBrains TeamCity: control builds, tests, agents and configs from AI coding assistants.
Implements 87 MCP tools spanning two operational modes—Dev (safe CI/CD operations like build triggering and log inspection) and Full (complete infrastructure management including build config creation and parameter CRUD). Built with Node.js using a singleton TeamCity REST API client, Zod for input validation, and centralized configuration with sensiti
About mcp-jetbrains
JetBrains/mcp-jetbrains
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
**Deprecated notice applies — this functionality is now built into IntelliJ-based IDEs 2025.2+.** This proxy server enabled external MCP clients (VS Code, Claude Desktop) to access IDE capabilities by proxying requests through a Node.js server to the IDE's built-in webserver, supporting multi-IDE scenarios via configurable host/port targeting. Architecture relied on stdio transport with environment-based configuration for host discovery and optional diagnostic logging.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work