Enables natural language control of JetBrains TeamCity CI/CD server, allowing users to trigger builds, monitor build status, fetch logs, analyze test failures, create build configurations, manage build steps and triggers, and configure VCS roots and agents.
Enables AI coding assistants to interact with JetBrains TeamCity CI/CD server through natural language commands. Supports triggering builds, monitoring status, analyzing test failures, and managing build configurations directly from development environments.
32
2,095 npm
31
MIT
Why this server?
Exposes JetBrains TeamCity as structured resources and tools for managing builds, including triggering, canceling, and pinning builds, setting tags, downloading artifacts, and performing advanced build searches with comprehensive filtering options.
Once configured, you can use natural language commands like:
"Search for failed builds in the last week"
"Why last deploy was failed"
"Search the most failed builds"
"Trigger a build for the main branch"
"Show me recent builds for project X"
"Pin the latest successful build"
"Cancel the running bui
12
MIT
Why this server?
Allows interaction with TeamCity CI/CD server, enabling build management (trigger, cancel, monitor), project navigation, test failure analysis, artifact access, change tracking, agent monitoring, queue management, and problem detection via natural language commands.
YouTrack MCP server and coding-agent pipelines. Every built-in YouTrack MCP tool plus deletes, sprints, attachments, history and reports, signed in with your login and password. Pipelines hand YouTrack issues to Claude Code, Kimi or any ACP agent and open the pull requests. One-command install into Claude, Cursor, VS Code, Zed, Codex and more.
2
MIT
Why this server?
Provides read-only tools for exploring and querying a JetBrains TeamCity server, including projects, build configurations, builds, logs, test results, problems, build queues, agents, artifacts, VCS changes, and server health.
Enables AI agents to explore a JetBrains TeamCity server through 29 strictly read-only tools covering projects, build configurations, build history and dependency chains, logs, test results, failure diagnostics, the queue, agents, artifacts, and VCS changes. All access is GET-only, so agents can inspect and troubleshoot CI without triggering, canceling, or modifying anything.