Jenkins MCP
The Jenkins MCP server allows you to manage Jenkins operations programmatically:
List Jenkins jobs: Retrieve all jobs configured in Jenkins
Trigger builds: Start a Jenkins build for a specific job with optional parameters
Get build status: Check the status of a specific build (defaults to latest if no build number provided)
CSRF crumb handling: Automatically handle Jenkins CSRF protection for secure API access
API Token Mode: Use Jenkins API tokens for authentication
Allows management of Jenkins operations including listing jobs, triggering builds with parameters, and checking build status
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Jenkins MCP list all jobs in the production folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Jenkins MCP
MCP server for managing Jenkins operations.
Installation
Installing via Smithery
To install Jenkins MCP for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @kjozsa/jenkins-mcp --client claudeInstalling Manually
uvx install jenkins-mcpRelated MCP server: jenkins-mcp-server
Configuration
Add the MCP server using the following JSON configuration snippet:
{
"mcpServers": {
"jenkins-mcp": {
"command": "uvx",
"args": ["jenkins-mcp"],
"env": {
"JENKINS_URL": "https://your-jenkins-server/",
"JENKINS_USERNAME": "your-username",
"JENKINS_PASSWORD": "your-password",
"JENKINS_USE_API_TOKEN": "false"
}
}
}
}CSRF Crumb Handling
Jenkins implements CSRF protection using "crumbs" - tokens that must be included with POST requests. This MCP server handles CSRF crumbs in two ways:
Default Mode: Automatically fetches and includes CSRF crumbs with build requests
Uses session cookies to maintain the web session
Handles all the CSRF protection behind the scenes
API Token Mode: Uses Jenkins API tokens which are exempt from CSRF protection
Set
JENKINS_USE_API_TOKEN=trueSet
JENKINS_PASSWORDto your API token instead of passwordWorks with Jenkins 2.96+ which doesn't require crumbs for API token auth
You can generate an API token in Jenkins at: User → Configure → API Token → Add new Token
Features
List Jenkins jobs
Trigger builds with optional parameters
Check build status
CSRF crumb handling for secure API access
Development
# Install dependencies
uv pip install -r requirements.txt
# Run in dev mode with Inspector
mcp dev jenkins_mcp/server.pyAvailable Tools
3 toolsget_build_statusB
Get build status
Args:
job_name: Name of the job
build_number: Build number to check, defaults to latest
Returns:
Build information dictionary
Inputs: job_name (required), build_number.
list_jobsB
List all Jenkins jobs
Inputs: no named parameters. Returns: result
trigger_buildB
Trigger a Jenkins build
Args:
job_name: Name of the job to build
parameters: Optional build parameters as a dictionary (e.g. {"param1": "value1"})
Returns:
Dictionary containing build information including the build number
Inputs: job_name (required), parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_build_status retrieves status information, list_jobs enumerates available jobs, and trigger_build initiates new builds. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (get_build_status, list_jobs, trigger_build). The verbs are descriptive and appropriate for their actions, and snake_case is used uniformly throughout.
With only 3 tools, the set feels thin for a Jenkins integration, which typically involves more operations like viewing logs, managing job configurations, or canceling builds. This limited scope may hinder agent workflows that require broader control.
The toolset is severely incomplete for Jenkins automation. It lacks essential operations such as viewing build logs, updating job configurations, canceling builds, or managing nodes/plugins. This creates significant gaps that will likely cause agent failures in common use cases.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn 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.46 npm14Apache 2.0
- FlicenseAqualityDmaintenanceExposes a Jenkins controller's REST API to MCP-compatible clients, enabling job management, build triggering, and log retrieval through natural language.114-
- AlicenseNot gradedqualityDmaintenanceEnables Jenkins CI/CD integration with job management, pipeline monitoring, artifact handling, and batch operations via MCP.4Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and external systems to programmatically trigger and monitor Jenkins jobs, retrieve build status and logs via MCP standards.-