Jenkins MCP Server

Jenkins pipeline monitoring, build status tracking, and job management for AI assistants.

Data last scanned today · Reviewed today

Overview

The Jenkins MCP Server allows AI models to interact directly with Jenkins CI/CD workflows. It provides tools for listing, searching, and triggering build jobs, as well as monitoring real-time build status and streaming console logs from pipelines. Beyond basic job execution, the server facilitates artifact management, queue monitoring, and multi-stage pipeline oversight. It is designed to be configured via environment variables, requiring a Jenkins URL, username, and API token to authenticate.

Our verdict

This server carries a high risk level with a security score of 19/100. The primary concern is that the repository has not received a commit in 356 days, suggesting it may lack maintenance. Additionally, it is a community-maintained project without an official link to the Jenkins organization. Due to these factors, it should be used with caution in sensitive CI/CD environments.

Supports listing and monitoring Jenkins build pipelines
Provides tools for managing build artifacts and queues
Features built-in exponential backoff for reliability

High security risk score of 19/100
Last code commit occurred over a year ago
Community-maintained without official vendor support

Setup

Claude Desktop

{
  "mcpServers": {
    "jenkins-mcp-server": {
      "args": [
        "-y",
        "@ashwinighuge/jenkins-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
trigger_job	Triggers a Jenkins job with optional parameters.	medium
get_job_info	Gets detailed information about a Jenkins job, including its parameters.	low
get_build_status	Gets the status of a specific build.	low
get_console_log	Retrieves the console log for a specific build.	low
list_jobs	Lists all available jobs on the Jenkins server with advanced filtering capabilities.	low
search_jobs	Search for Jenkins jobs using pattern matching with advanced filtering.	low
get_queue_info	Gets information about builds currently in the queue.	low
server_info	Gets basic information about the Jenkins server.	low
get_pipeline_status	Gets detailed pipeline stage status for Jenkins Pipeline job builds.	low
list_build_artifacts	List all artifacts for a specific Jenkins build.	low

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What software prerequisites are required to run this server?

You need Node.js 14.0.0 or higher, Python 3.12 or higher, and a Jenkins instance running version 2.401 or later.

›How do I authenticate the server with my Jenkins instance?

You must provide a Jenkins username and a generated API token via the JENKINS_USER and JENKINS_API_TOKEN environment variables.

›Does this server support different transport methods?

Yes, it supports STDIO transport, which is used for Claude Desktop, and streamable-http transport for use with an MCP Gateway.

›Can I configure cache TTLs and sizes for performance?

Yes, you can customize performance caching for static, semi-static, dynamic, and short-lived data by setting environment variables like JENKINS_CACHE_STATIC_TTL and JENKINS_CACHE_STATIC_SIZE.

›Is it possible to run the server without a global npm installation?

Yes, you can execute the server directly using npx or by cloning the repository and running the bin/jenkins-mcp.js file.

Badge

Maintain this server? Add the live badge to your README.