Skip to main content
Glama
dittops

jenkins-mcp

by dittops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to jenkins-mcp

No user-submitted related servers found.

    Related Servers

    • Jenkins MCP Server

      AshwiniGhuge3012
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with a Jenkins CI/CD server. Allows you to trigger jobs, check build statuses, and manage your Jenkins instance through MCP.
      17 npm
      14
      Apache 2.0

    • Jenkins MCP

      kjozsa
      A
      license
      B
      quality
      D
      maintenance
      Enables managing Jenkins operations like listing jobs, triggering builds, and checking build statuses through a configurable MCP server.
      3
      10
      Apache 2.0

    • Jenkins MCP

      programsummer
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing multiple Jenkins instances via REST API, supporting job/build queries, triggering builds, and logs with optional read-only mode.
      MIT

    • Jenkins MCP Proxy

      ravi11196
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and external systems to programmatically trigger and monitor Jenkins jobs, retrieve build status and logs via MCP standards.
      -

    • Jenkins MCP Server

      grglzrv
      A
      license
      Not graded
      quality
      A
      maintenance
      A production-ready MCP server for Jenkins that enables managing jobs, pipelines, builds, and nodes through natural language, with configurable security and guardrails.
      2
      MIT
    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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct role in the Jenkins workflow: list available actions, trigger an action, fetch build status/result, and read console logs. The descriptions make it clear when to use each one, so an agent should not confuse them.

    Naming Consistency5/5

    All tool names follow the same snake_case `verb_jenkins_noun` pattern: `list_jenkins_actions`, `run_jenkins_action`, `get_jenkins_build`, `get_jenkins_console`. The naming is uniform and predictable.

    Tool Count5/5

    Four tools is well-scoped for this server's design: a discovery tool, a generic action trigger, a build status poller, and a console log reader. Each tool earns its place and there is no redundancy.

    Completeness4/5

    The discover-trigger-poll-debug lifecycle is well covered, giving agents a usable path from start to diagnosis. Minor gaps exist, such as no explicit cancellation, artifact retrieval, or listing builds independently of a just-triggered run, but these are workable limitations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources