MCP Jenkins

About

a Python MCP server for Jenkins (lanbaoshen/mcp-jenkins, published to PyPI as mcp-jenkins) and the alternative to the official Jenkins MCP plugin: where the plugin has to be installed into the controller from the update centre, this one runs beside Jenkins and talks to it over the ordinary REST API, so you can point it at a Jenkins you do not administer. Install it with uvx mcp-jenkins, pip install mcp-jenkins, or the ghcr.io/lanbaoshen/mcp-jenkins container. Credentials go in as --jenkins-url, --jenkins-username and --jenkins-password (an API token works in place of the password), and on the HTTP transport the same three can be supplied per-connection as the x-jenkins-url, x-jenkins-username and x-jenkins-password headers, which is what lets one running instance serve several Jenkins controllers. Three transports are available via --transport: stdio (the default), sse, and streamable-http, which listens on 0.0.0.0:9887 unless --host and --port say otherwise. The tool set is wider than most Jenkins integrations. Jobs and pipelines: get_item, get_item_config, get_item_parameters, get_all_items, query_items for pattern search, and build_item to trigger. Builds: get_build, get_build_console_output, get_build_parameters, get_build_test_report, get_build_scripts, get_running_builds and stop_build, plus get_all_build_artifacts, get_build_artifact and get_build_artifact_url for pulling artifacts out of a finished run. Queue: get_all_queue_items, get_queue_item, cancel_queue_item. Agents: get_all_nodes, get_node, get_node_config. The plugin tools are the part with no equivalent elsewhere — get_all_plugins, get_plugin, get_plugins_with_updates, get_plugins_with_backup, get_plugin_dependency_graph (Graphviz output), and get_plugins_with_problems, which reports missing dependencies and version mismatches and turns a plugin upgrade audit into one question. Two flags matter for safety. run_groovy_script executes arbitrary Groovy on the controller, which is full remote code execution against your CI; --read-only disables it along with every other mutating tool and is the right default for an agent that only needs to read build state. --jenkins-timeout defaults to 5 seconds, which is often too short for a large get_all_items on a busy controller.

Installation

uvx mcp-jenkins

Setting up MCP Jenkins

1. 1.Install the server

   Published to PyPI as mcp-jenkins. uvx is the recommended route because it needs no virtualenv of your own; pip and a prebuilt container image are both supported alternatives.

   shell

   # recommended
   uvx mcp-jenkins
   
   # or
   pip install mcp-jenkins && mcp-jenkins
   
   # or
   docker run -p 9887:9887 --rm ghcr.io/lanbaoshen/mcp-jenkins:latest --transport streamable-http

2. 2.Create a Jenkins API token

   Under your Jenkins user page, Security → API Token. Pass it as --jenkins-password; the server treats a token and a password identically, and a token is revocable without changing your login. The permissions of that Jenkins user are the real boundary — the server adds none of its own.

3. 3.Point your client at it

   stdio is the default transport and takes the connection details as command-line arguments. This shape works in Claude Desktop, Cursor, VS Code Copilot Chat and JetBrains Copilot alike.

   claude_desktop_config.json

   {
     "mcpServers": {
       "jenkins": {
         "command": "uvx",
         "args": [
           "mcp-jenkins",
           "--jenkins-url=https://jenkins.example.com",
           "--jenkins-username=you",
           "--jenkins-password=<api-token>",
           "--read-only"
         ]
       }
     }
   }

4. 4.Optional — run it once for several controllers

   With --transport streamable-http the server listens on 0.0.0.0:9887 (override with --host and --port) and accepts the connection details per request as the x-jenkins-url, x-jenkins-username and x-jenkins-password headers. That is what lets one running instance serve several Jenkins controllers instead of one process each. sse is available too, for clients that still want it.

   shell

   uvx mcp-jenkins --transport streamable-http

What the server can do

Jobs, builds, the queue, agents, and — uniquely — the plugin inventory. build_item, stop_build, cancel_queue_item and run_groovy_script mutate; --read-only removes all of them.

What people use it for

Which one should you use?

Categories

Works With

Frequently Asked Questions