Skip to main content
Glama
grglzrv

Jenkins MCP Server

by grglzrv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Jenkins MCP Server

No user-submitted related servers found.

    Related Servers

    • Jenkins AI Optimizer

      karadhub
      A
      license
      Not graded
      quality
      D
      maintenance
      Enterprise-grade MCP server for Jenkins CI/CD integration that enables AI assistants to diagnose build failures, analyze pipelines, and search logs through natural conversation.
      6
      GPL 3.0

    • 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

    • 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
      23 npm
      MIT

    • 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.
      36 npm
      14
      Apache 2.0

    • 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
      177 npm
      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/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action, and where overlaps exist (create_job_from_xml vs create_pipeline_job vs create_multibranch_pipeline, get_queue vs get_queue_item, get_build_info vs get_build_console) the descriptions explicitly state when to use which. No two tools appear interchangeable.

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout (list_jobs, get_job, delete_job, trigger_build, stop_build, get_queue_item, set_node_offline). The single jenkins_admin_request deviates slightly but remains readable and clearly scoped.

    Tool Count4/5

    At 24 tools this is on the heavier side, but the Jenkins domain is broad (jobs, builds, queue, nodes, admin) and each tool covers a genuinely distinct operation, so nothing feels redundant. Slightly high for a single server, though every tool earns its place.

    Completeness4/5

    Strong lifecycle coverage: job CRUD/config, pipeline creation, build trigger/stop/info/console, queue inspection and cancellation, nodes, plus an admin escape hatch for anything else. Minor gaps remain (e.g. build artifacts, credential listing, views), but the admin tool largely backstops them.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources