Skip to main content
Glama
Pawangunjkar

Jenkins MCP Server

by Pawangunjkar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Jenkins MCP Server

No user-submitted related servers found.

    Related Servers

    • Jenkins Server MCP

      hekmon8
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Jenkins CI/CD servers, providing tools to check build statuses, trigger builds, and retrieve build logs.
      3
      15
      MIT

    • Jenkins MCP Server

      andreimatveyeu
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol (MCP) server that enables AI tools like chatbots to interact with and control Jenkins, allowing users to trigger jobs, check build statuses, and perform other Jenkins operations through natural language.
      MIT

    • Jenkins MCP

      Oshaani-AI
      A
      license
      A
      quality
      C
      maintenance
      MCP server that connects AI agents to Jenkins, supporting stdio and HTTP transports with tools for jobs, builds, logs, and queue management.
      9
      108 npm
      MIT

    • MCP-Jenkins

      gcorroto
      A
      license
      B
      quality
      D
      maintenance
      A server that enables interaction with Jenkins CI/CD pipelines from any compatible MCP client (like Claude Desktop), allowing users to manage jobs, builds, coverage reports, and other Jenkins functionality through natural language.
      11
      7 npm
      MIT

    • Jenkins MCP Server

      umishra1504
      A
      license
      B
      quality
      D
      maintenance
      Enables comprehensive Jenkins automation through MCP interface, allowing users to manage builds, jobs, artifacts, and queues with natural language commands. Supports build triggering, monitoring, artifact retrieval, and system status checks with automatic CSRF protection and authentication.
      14
      108 npm
      MIT

    • jenkins-mcp

      mcpland
      A
      license
      B
      quality
      B
      maintenance
      Provides AI assistants with full access to Jenkins CI/CD systems, enabling querying, managing, and controlling Jenkins jobs, builds, nodes, and queues through natural language.
      22
      502 npm
      1
      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

    B3.2/5.0

    Scored across 53 tools

    Disambiguation4/5

    Most tools are clearly distinct, targeting specific resource-action pairs (jobs, builds, nodes, views, credentials, plugins, queue). A few could cause minor confusion, such as jenkins_get_queue vs jenkins_get_queue_item, or jenkins_get_job vs jenkins_get_job_config, but the descriptions differentiate them well. The session management tools are also well-separated.

    Naming Consistency4/5

    The uniform 'jenkins_' prefix and verb_noun pattern (get_job, create_job, delete_job, enable_job) are highly consistent throughout. Minor deviations exist like jenkins_system_info vs the expected jenkins_get_system, and jenkins_run_groovy_script doesn't follow verb_noun for a specific resource, but the pattern is otherwise strong.

    Tool Count2/5

    At 53 tools, this is substantial for a CI/CD server. While Jenkins is a large domain covering jobs, builds, nodes, views, credentials, plugins, queue, and system operations, the volume is heavy and could overwhelm an agent. Some tools like jenkins_get_last_build, jenkins_get_last_successful_build, and jenkins_get_last_failed_build could arguably be consolidated, but the breadth generally tracks the genuine complexity of Jenkins.

    Completeness5/5

    Coverage is exceptionally comprehensive. The tool set spans job lifecycle (create/get/update/delete/copy/rename/enable/disable), build operations (build/info/log/stop/delete/last variants), node management, views, credentials, plugins, the build queue, and system administration. The only minor gaps are niche operations like credential updates or job-level artifact downloads, but nothing that would create dead ends in core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources