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 "Install 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 MCPlist 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: kom
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.py