teamcity-cli — Claude Code plugin: what it does, how to install
This plugin lets Claude Code work with TeamCity through its CLI, from inspecting builds and logs to starting jobs and checking agents.
/plugin install teamcity-cli@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-community
/plugin install teamcity-cli@claude-community
/plugin marketplace add anthropics/claude-plugins-officialWhat teamcity-cli does
This plugin gives Claude Code access to TeamCity’s command-line client. An agent can inspect builds, read logs, start jobs with a selected branch or revision, review the queue, and open a shell on a build agent.
Run teamcity auth login before using the CLI so it can remember the server and credentials. Commands expose --json and --plain output for scripts, while teamcity api covers REST requests that have no dedicated command. Setting TEAMCITY_RO=1 blocks writes and remote shells, so commands such as agent exec and agent term cannot perform those actions in that mode.
The CLI can store several server connections and switch between them. In Claude Code, install the plugin from the official marketplace before asking the agent to use TeamCity.
What it helps with
- inspect the latest build for a branch
- start a job with a chosen revision
- find failures in a build log
- check queued jobs and agent status
Example prompts for the agent
- Use
teamcity run list --user @me --branch @this --limit 1to show the latest build for the current branch. - Start
MyProject_Buildonmainand keep watching it withteamcity run start MyProject_Build --branch main --watch. - List the jobs waiting in TeamCity with
teamcity queue list, then explain their current state.
How to install teamcity-cli
Plugin marketplace
/plugin install teamcity-cli@claude-plugins-official/plugin marketplace add anthropics/claude-plugins-community/plugin install teamcity-cli@claude-community/plugin marketplace add anthropics/claude-plugins-officialStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about teamcity-cli
How do I install teamcity-cli in Claude Code?
Add the official marketplace with /plugin marketplace add anthropics/claude-plugins-official, then install the plugin with /plugin install teamcity-cli@claude-plugins-official.
What does teamcity-cli do?
It gives Claude Code CLI access to TeamCity builds, logs, jobs, queues, and agents. It can also send direct requests to the TeamCity REST API.
What does TEAMCITY_RO=1 change?
This setting blocks write operations and remote shells through agent exec and agent term. Server-side permissions remain the security boundary.
Source text
SKILL.md · Apache-2.0
# TeamCity CLI [](https://github.com/JetBrains) [](https://github.com/JetBrains/teamcity-cli/releases/latest) `teamcity` is the official command-line client for [TeamCity](https://www.jetbrains.com/teamcity/). It covers the day-to-day — starting builds, tailing logs, digging through the queue — and the odd jobs too: shelling into build agents, editing job settings, raw REST calls when nothing else fits.   Full documentation, including installation, authentication, and a command reference, lives at [jb.gg/tc/docs](https://jb.gg/tc/docs). ## Install **macOS (Homebrew):** ```bash brew install jetbrains/utils/teamcity ``` **Linux:** ```bash curl -fsSL https://jb.gg/tc/install | bash ``` The install script also works on macOS. New installs use `~/.local/bin` without sudo; rerunning it updates an existing unmanaged installation in place. Missing Bash/Zsh PATH entries are added automatically. Restart your shell afterward, or use the printed PATH command. **Windows (Winget):** ```powershell winget install JetBrains.TeamCityCLI ``` **npm:** ```bash npm install -g @jetbrains/teamcity-cli ``` <details> <summary>More installation methods (deb, rpm, Chocolatey, Scoop, build from source)</summary> **Debian/Ubuntu:** ```bash curl -fsSLO https://github.com/JetBrains/teamcity-cli/releases/latest/download/teamcity_linux_amd64.deb sudo dpkg -i teamcity_linux_amd64.deb ``` **RHEL/Fedora:** ```bash sudo rpm -i https://github.com/JetBrains/teamcity-cli/releases/latest/download/teamcity_linux_amd64.rpm ``` **Arch Linux (AUR):** ```bash yay -S teamcity-bin ``` **PowerShell:** ```powershell irm https://jb.gg/tc/install.ps1 | iex ``` **CMD:** ```cmd curl -fsSL https://jb.gg/tc/install.cmd -o install.cmd && install.cmd && del install.cmd ``` **Chocolatey:** ```powershell choco install teamcitycli ``` **Scoop:** ```powershell scoop bucket add jetbrains https://github.com/JetBrains/scoop-utils scoop install teamcity ``` **Build from source:** ```bash go install github.com/JetBrains/teamcity-cli/tc@latest ``` See the [getting started guide](https://www.jetbrains.com/help/teamcity/teamcity-cli-get-started.html) for the full walkthrough. </details> ## Usage For security, redirects never downgrade HTTPS or forward request headers to another origin. Cross-origin artifact downloads remain supported without credentials. Log in once and the CLI remembers the server: ```bash teamcity auth login ``` Then: ```bash # my latest build on this branch teamcity run list --user @me --branch @this --limit 1 # start a build and stay attached to it teamcity run start MyProject_Build --branch main --watch # pin different revisions in a job with multiple VCS roots teamcity run start MyProject_Build --revision AppRepo=abc123 --revision AssetsRepo=@main # logs from the latest build of a job teamcity run log --job MyProject_Build # what's sitting in the queue teamcity queue list # shell into a build agent teamcity agent term Agent-Linux-01 ``` One naming note: TeamCity says *build* and *build configuration*; the CLI says `run` and `job`. The [glossary](https://www.jetbrains.com/help/teamcity/teamcity-cli-glossary.html) has the full mapping. Set `TEAMCITY_RO=1` to block writes and remote shells (`agent exec` and `agent term`). Use server-side permissions for a security boundary. Every command takes `--json` or `--plain` for [scripting](https://www.jetbrains.com/help/teamcity/teamcity-cli-scripting.html), and `--web` opens the matching page in the TeamCity UI. When no command covers what you need, `teamcity api` calls the REST API directly with your stored credentials. You can also log in to several servers and switch between them — see [configuration](https://www.jetbrains.com/help/teamcity/teamcity-cli-configuration.html). For a queued run, `teamcity run view <id>` reports agent and cloud-image compatibility, including unmet requirements, when the server supports it. Large pools are summarized; use `--json` and read `.compatibility` for every entry. ## Commands Artifact downloads are confined to `--output`; failed or incomplete transfers preserve existing files. | Group | Commands | |--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **auth** | `login`, `logout`, `status` | | **run** | `list`, `start`, `view`, `watch`, `log`, `tree`, `changes`, `tests`, `diff`, `cancel`, `download`, `artifacts`, `restart`, `pin`/`unpin`, `tag`/`untag`, `comment` | | **job** | `list`, `view`, `create`, `tree`, `pause`/`resume`, `step list`/`view`/`add`/`delete`, `param list`/`get`/`set`/`delete`, `settings list`/`get`/`set` | | **project** | `list`, `view`, `create`, `tree`, `vcs list`/`view`/`create`/`test`/`delete`, `ssh list`/`generate`/`upload`/`delete`, `cloud profile`/`image`/`instance`, `connection list`/`view`/`create github-app`/`create docker`/`authorize`/`delete`, `param`, `token get`/`put`, `settings export`/`status`/`validate` | | **pipeline** | `list`, `view`, `create`, `validate`, `pull`, `push`, `schema` (enabled runners/features), `delete` | | **queue** | `list`, `approve`, `remove`, `top` | | **agent** | `list`, `view`, `term`, `exec`, `jobs`, `authorize`/`deauthorize`, `enable`/`disable`, `move`, `reboot` | | **pool** | `list`, `view`, `link`/`unlink` | | **server** | `plugin upload` (optionally with `--hot-reload`) | | **api** | Raw REST API access | | **link** | Bind this repository to a TeamCity project via `teamcity.toml` | | **config** | `list`, `get`, `set` | | **alias** | `set`, `list`, `delete` | | **skill** | `list`, `install`, `remove`, `update` | | **update** | Check for and install CLI updates (`--check`/`--json` for status only, `--yes` for non-interactive installation) | Run `teamcity <command> --help` for usage, or see the [command reference](https://www.jetbrains.com/help/teamcity/teamcity-cli-commands.html). ## For AI agents The CLI ships with an [Agent Skill](https://agentskills.io) that teaches coding agents (Claude Code, Cursor, and others) how to drive `teamcity`: ```bash teamcity skill install # auto-detects installed agents teamcity skill install --project # install to current project only teamcity skill update # update to the version bundled with teamcity teamcity skill remove # uninstall ``` or specifically for **Claude Code**, install the `teamcity` plugin, which bundles these skills from [JetBrains/teamcity-skills](https://github.com/JetBrains/teamcity-skills): ```bash /plugin marketplace add JetBrains/teamcity-skills /plugin install teamcity@teamcity ``` The plugin ships the skills only — install the `teamcity` CLI itself as above. See [AI agent integration](https://www.jetbrains.com/help/teamcity/teamcity-cli-ai-agent-integration.html) for details. ## Learn more - [Getting started](https://www.jetbrains.com/help/teamcity/teamcity-cli-get-started.html) – install, authenticate, and run your first commands - [Configuration](https://www.jetbrains.com/help/teamcity/teamcity-cli-configuration.html) – config file, environment variables, multi-server setup, shell completion - [Scripting and automation](https://www.jetbrains.com/help/teamcity/teamcity-cli-scripting.html) – JSON output, plain text mode, CI/CD integration - [Aliases](https://www.jetbrains.com/help/teamcity/teamcity-cli-aliases.html) – create custom command shortcuts ## Contributing TeamCity CLI is open source under the Apache-2.0 license. Bug reports and pull requests are welcome — [CONTRIBUTING.md](CONTRIBUTING.md) covers how the project is built and tested. `project settings status` reports the server’s runtime message and missing DSL context parameters. Its “Recorded” timestamp is when the status was recorded, not the last successful sync. Connections listed or selected with `--project` include parent projects, including `_Root`. Delete an inherited connection from its owning project.
© JetBrains · Apache-2.0 · JetBrains/teamcity-cli