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.
This project allows software developers to manage their CI/CD processes within JetBrains TeamCity directly from their AI coding assistants. It takes commands given in natural language within the AI assistant and translates them into actions like triggering builds, checking test failures, or managing build configurations. The primary users are developers leveraging AI assistants to streamline their software development and operations workflows.
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
This project helps software developers integrate AI tools and other applications with their JetBrains IDEs like IntelliJ, PyCharm, or WebStorm. It acts as a bridge, allowing external applications (like VS Code or Claude Desktop) to send and receive information from your open JetBrains IDE. Developers would use this to enhance their coding environment with third-party tools that benefit from IDE context.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work