Jenkins MCP Server

What avisangle/jenkins-mcp-server MCP server does

The avisangle/jenkins-mcp-server MCP server exposes Jenkins CI/CD operations as MCP tools. It can list, search, inspect, and trigger jobs, including jobs organized inside nested folders. Job searches support wildcard patterns, optional regular expressions, job-type filters, folder-depth limits, status filters, build-result filters, and enabled-only filtering.

Build-focused tools retrieve build status, duration, timestamps, executor details, console output, and summarized logs. Pipeline jobs can be inspected stage by stage, including stage status, duration, and logs. Artifact tools list files from a build, download a selected artifact, or search for matching artifacts across multiple builds.

How it works

The server authenticates to Jenkins with a Jenkins URL, username, and API token. It handles Jenkins CSRF crumb tokens automatically and includes retry behavior with exponential backoff. Input validation is provided through Pydantic-based validation.

MCP clients can communicate with the server over STDIO, the default transport intended for local clients such as Claude Desktop, or over Streamable HTTP. HTTP mode accepts host and port settings and is intended for MCP gateways or remote connections. Batch tools can trigger multiple jobs in parallel, monitor a batch operation, and cancel one. Queue tools provide information about pending Jenkins builds.

Caching is divided into five tiers for different data lifetimes. The server also provides tools to inspect cache statistics, clear cached data, and warm the cache with commonly used information.

Setup and configuration

Running the avisangle/jenkins-mcp-server MCP server requires Node.js 14 or newer, Python 3.12 or newer, and a Jenkins installation; Jenkins 2.401 or newer is recommended. The repository installation process uses npm install, followed by pip install -e . or an equivalent editable installation with uv.

Set JENKINS_URL, JENKINS_USER, and JENKINS_API_TOKEN before starting the server. Optional settings control retry limits and delays, cache time-to-live values and sizes, log and content limits, artifact download size, and the HTTP host and port. A Jenkins API token is created from the user's Jenkins configuration page.

The documented STDIO entry point is node bin/jenkins-mcp.js. Streamable HTTP can be selected with --transport streamable-http, along with --port and --host options. The README includes a Claude Desktop configuration that starts this entry point and passes the Jenkins settings as environment variables.

Tools and capabilities

The avisangle/jenkins-mcp-server MCP server provides tools for:

• Triggering one job, searching and triggering matching jobs, or triggering multiple jobs in parallel.
• Listing jobs recursively, searching by pattern, and inspecting job or folder details.
• Reading build status, console logs, summarized logs, and pipeline stage status.
• Listing, downloading, and searching build artifacts.
• Monitoring and canceling batch operations and inspecting the Jenkins queue.
• Reading Jenkins server information and managing cache statistics, contents, and warm-up operations.

Limitations and notes

Jenkins credentials are required, and the server depends on access to the target Jenkins instance. Artifact downloads have a configurable maximum size, with a documented default of 50 MB. Console and general content responses also have configurable size limits. The README documents 21 tools, so the available operations are centered on the listed Jenkins job, build, pipeline, artifact, queue, batch, and cache functions rather than general Jenkins administration.