Skip to main content
Glama
CircleCI-Public

mcp-server-circleci

Official
by CircleCI-Public
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-circleci

No user-submitted related servers found.

    Related Servers

    • cursor-mcp-server

      bbarney7
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server wrapping the Cursor CLI agent, enabling Claude Code and other MCP clients to delegate tasks to Cursor's AI agent for file writing, bash commands, and codebase queries.
      -

    • codemagic_mcp

      Zfinix
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Codemagic CI/CD API, enabling app management, build operations, artifact handling, cache control, and team management through natural language.
      14 npm
      3
      MIT

    • mcp-codemagic

      musictechlab
      A
      license
      A
      quality
      D
      maintenance
      This MCP server enables users to manage Codemagic CI/CD builds directly from Claude Code, including listing apps, triggering builds, checking status, and canceling builds.
      6
      MIT

    • cursor-agent-bridge

      cybas
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets Claude Code or any MCP client delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions and tools for diffing and pushing changes.
      12 npm
      MIT

    • mcp-zuul

      imatza-rh
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Zuul CI. Debug build failures by asking questions, not clicking through web UIs. Read-only access to any Zuul instance — builds, logs, pipelines, jobs, and live status. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.
      44
      115 PyPI
      21
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools have distinct purposes (e.g., config_helper vs. find_flaky_tests), but there is notable overlap between run_pipeline, run_evaluation_tests, and rerun_workflow, which all involve triggering or re-running CI workflows. Additionally, analyze_diff seems unrelated to CircleCI's core domain, creating confusion about the server's scope. Descriptions help clarify, but the overlap and outlier reduce clarity.

    Naming Consistency4/5

    The majority of tools follow a consistent verb_noun or verb_adjective_noun pattern (e.g., list_followed_projects, get_build_failure_logs, find_underused_resource_classes). However, there are minor deviations like config_helper (noun_verb) and analyze_diff (verb_noun without underscore), which slightly break the pattern but do not severely impact readability.

    Tool Count3/5

    With 16 tools, the count is borderline high for a CI-focused server, especially given the inclusion of prompt-related tools (create_prompt_template, recommend_prompt_template_tests) that seem out of scope. This makes the set feel somewhat bloated and less focused on core CircleCI operations, though it's not extreme.

    Completeness4/5

    For CircleCI operations, the surface covers key areas like project listing, pipeline management, debugging, and usage analysis, with good lifecycle coverage (e.g., run_pipeline, rerun_workflow, get_build_failure_logs). However, gaps exist in areas like user management or detailed configuration editing, and the prompt tools are tangential, slightly reducing coherence for the main domain.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources