Skip to main content
Glama
Sign In
TeamCity MCP Server

TeamCity MCP Server

by Daghis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to TeamCity MCP Server

No user-submitted related servers found.

    Related Servers

    • TeamCity MCP Server

      hex
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of TeamCity CI/CD operations through natural language commands, including builds, projects, tests, artifacts, and more.
      21 npm
      MIT

    • Jenkins MCP Server

      Anil-appari007
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jenkins CI/CD systems through natural language, providing build management, job monitoring, log analysis, and debugging capabilities.
      MIT

    • Atlassian Bamboo MCP Server

      norus
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with Atlassian Bamboo CI/CD, allowing natural language queries to check build status, fetch logs, trigger builds, and manage deployments.
      27
      791 npm
      6
      MIT

    • TeamCity

      desty2k
      A
      license
      Not graded
      quality
      C
      maintenance
      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.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action (projects, build configs, builds, queue, tests, problems, artifacts), and descriptions clarify close pairs like get_build vs get_build_status vs get_build_results. However, cancel_queued_build overlaps heavily with cancel_build (which explicitly handles 'running or queued' builds), and list_problems vs list_problem_occurrences plus get_test_details vs list_test_failures have blurry boundaries.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (list_projects, get_build, trigger_build, download_build_artifact), with only trivial exceptions like ping. Singular/plural distinctions (download_build_artifact vs download_build_artifacts) are used predictably.

    Tool Count3/5

    At 32 tools the surface is heavy for any single agent context, though the CI-server domain is genuinely broad (projects, configs, queue, tests, problems, artifacts, server ops). Some tools feel like bloat or could be merged, e.g. cancel_queued_build alongside cancel_build, and the singular/plural artifact download pair.

    Completeness3/5

    Core CI workflows are well covered: inspect projects/configs, list/trigger/cancel/wait on builds, fetch logs and artifacts, and review tests, problems, changes, and investigations. Notable gaps remain around agents (why a build is queued, agent status), VCS roots, tags/pinning, and any create/update/delete of projects or build configurations, which limits write-side lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources