jenkins

An MCP server for interacting with a Jenkins server. Allows you to trigger jobs, check build statuses, and manage your Jenkins instance through MCP.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio ashwinighuge3012-jenkins-mcp-server jenkins-mcp \
  --env JENKINS_URL="http://your-jenkins-server:8080" \
  --env JENKINS_USER="your-username" \
  --env JENKINS_API_TOKEN="your-api-token"

How to use

This Jenkins MCP Server provides a production-ready interface to manage Jenkins CI/CD tasks via the MCP (Model Context Protocol). It exposes a set of tools that let you trigger jobs, query job details, monitor build status, fetch console logs, and manage artifacts across multiple builds. It supports both STDIO mode for Claude Desktop or local clients and an HTTP transport mode for MCP Gateway integration. The available tools include trigger_job for starting jobs with optional parameters, get_job_info to retrieve job metadata, get_build_status to check a specific build, get_console_log to stream logs, and list_jobs or search_jobs to discover and filter Jenkins jobs with advanced criteria. You can configure Jenkins connection details via environment variables and tune performance with the included cache and retry settings. To start using it, install the MCP server, set Jenkins credentials, and run the jenkins-mcp executable, then interact with the exposed tools to manage your Jenkins CI/CD pipelines.

How to install

Prerequisites:

Node.js 14.0.0 or higher
npm (comes with Node.js) or yarn
Jenkins 2.401+ with API token access

Installation steps:

Global installation (recommended):
- npm install -g @ashwinighuge/jenkins-mcp-server
- Verify installation: jenkins-mcp --help
Development setup (optional):
- git clone https://github.com/AshwiniGhuge3012/jenkins-mcp-server
- cd jenkins-mcp-server
- npm install
- (Optional) install Python dependencies if you plan to run Python components: pip install -r requirements.txt
- Run locally: node bin/jenkins-mcp.js --help
Environment configuration:
- Create a .env file or export environment variables to configure Jenkins connection and MCP server options (see README for example variables).
Run the server:
- For STDIO mode (default): jenkins-mcp
- For HTTP mode: jenkins-mcp --transport streamable-http --port 8010

Additional notes

Tips and notes:

Ensure JENKINS_URL, JENKINS_USER, and JENKINS_API_TOKEN are set correctly to avoid authentication errors.
The server supports multiple transport modes; use STDIO for Claude Desktop integration or HTTP for MCP Gateway usage.
If behind proxies or firewalls, configure MCP_HOST and MCP_PORT accordingly.
Adjust caching and retry behavior via the provided JENKINS_CACHE_* and JENKINS_RETRY_* environment variables to optimize performance and reliability.
For security, never commit credentials to source control; prefer environment-based configurations or secret managers.
Use the available tools to automate common workflows: trigger_job to start builds, get_build_status and get_console_log for monitoring, and list_jobs/search_jobs to discover relevant Jenkins jobs efficiently.