Can AI agents automate TeamCity?

TeamCity is automatable today through its REST API and official CLI. This record is JetBrains TeamCity (on-premises and Cloud), not Jenkins or Azure DevOps. REST lives under /app/rest with Swagger at /app/rest/swagger.json. Preferred authentication is a personal access token as Authorization Bearer. Basic HTTP auth via /httpAuth/app/rest and guest access via /guestAuth/app/rest (when enabled) are also documented. The official teamcity CLI starts builds, tails logs, manages agents, emits --json, and can send arbitrary REST via teamcity api. First-party MCP is at /app/mcp with tools for build logs, REST GET/POST, and pipelines. Safe mode limits writes to personal build-queue posts unless teamcity.ai.mcp.braveMode.enabled is true. JetBrains states the CLI covers a wider operational surface than MCP. Official REST SDK status was not established; Kotlin DSL and YAML pipelines are recorded as scripting. Computer-use viability is unassessed. API and CLI both score 8; API is the best path because the CLI and MCP consume it. MCP scores 7 as official but narrower and safe-mode gated.

Best path today: api · Overall automatability: 8/10