Integration

TeamCity integration

JetBrains TeamCity self-hosted CI/CD server REST API. Manage projects and build configurations, trigger and monitor builds, control the build queue, manage build agents, users, and VCS roots.

Connect TeamCity How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in TeamCity.Built from the 21 TeamCity tools below, on the connection you add once.

Common TeamCity use cases

Stop a stuck or hanging build
Cancel a duplicate queued build
Decommission a deprecated project
Monitor pending build queue depth
Audit users on a TeamCity instance
Disable an agent during maintenance
Trigger a CI build after a code push
Audit VCS roots in a TeamCity instance
Clean up obsolete build configurations
Check whether a build succeeded or failed

What you can do with TeamCity

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Build, 4 operations

cancel_running_buildCancel running buildPOSTStop a currently running TeamCity build
get_buildGet buildGETRetrieve a single TeamCity build by locator including status, state, timing and branch
list_buildsList buildsGETList TeamCity builds with locator-based filters (build configuration, status, branch, etc.)
trigger_buildTrigger buildPOSTQueue a new TeamCity build for the specified build configuration

Project, 4 operations

create_projectCreate projectPOSTCreate a new TeamCity project under a parent project
delete_projectDelete projectDELETEPermanently delete a TeamCity project and all its build configurations and sub-projects
get_projectGet projectGETRetrieve a single TeamCity project by locator including its build configurations and sub-projects
list_projectsList projectsGETList all TeamCity projects with their IDs, names and parent project links

Agent, 3 operations

get_agentGet agentGETRetrieve a single build agent with its connection, authorization and enabled state
list_agentsList agentsGETList TeamCity build agents with their connection, authorization and enabled state
set_agent_enabledSet agent enabledPUTEnable or disable a TeamCity build agent

Build type, 3 operations

delete_build_typeDelete build typeDELETEPermanently delete a build configuration and all its build history
get_build_typeGet build typeGETRetrieve a single TeamCity build configuration including its parameters and steps
list_build_typesList build typesGETList all TeamCity build configurations (buildTypes), optionally filtered by project

Queue, 2 operations

cancel_queued_buildCancel queued buildPOSTCancel a build that is still waiting in the TeamCity build queue
list_build_queueList build queueGETList builds currently waiting in the TeamCity build queue

User, 2 operations

get_current_userGet current userGETRetrieve information about the currently authenticated TeamCity user
list_usersList usersGETList all TeamCity users with their usernames and IDs

Parameter, 1 operation

get_build_type_parametersGet build type parametersGETList all parameters defined on a TeamCity build configuration

Server, 1 operation

get_server_infoGet server infoGETRetrieve TeamCity server version, build number and start time

Vcs root, 1 operation

list_vcs_rootsList vcs rootsGETList all VCS roots configured in TeamCity (Git, SVN, Perforce, etc.)

Use TeamCity from Claude Code, Cursor or Codex

Connect TeamCity in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TeamCity operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect TeamCity

Create your workspace
Sign up free. Nothing to install.
Connect TeamCity once
Add your TeamCity connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

TeamCity integration FAQ

What can you do with the TeamCity integration?

LiveContext exposes 21 operations on TeamCity, covering build, project, agent and build type. Common uses include Stop a stuck or hanging build, Cancel a duplicate queued build and Decommission a deprecated project.