MCP server for managing Jenkins operations
Listed on its own since 2026-09-26. Until then it was part of cams-jenkins-mcp, where its earlier checks remain.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-jenkins-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Jenkins MCP [](https://smithery.ai/server/@kjozsa/jenkins-mcp) MCP server for managing Jenkins operations. <a href="https://glama.ai/mcp/servers/7j3zk84u5p"> <img width="380" height="200" src="https://glama.ai/mcp/servers/7j3zk84u5p/badge" alt="Jenkins MCP server" /> </a> ## Installation ### Installing via Smithery To install Jenkins MCP for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@kjozsa/jenkins-mcp): ```bash npx -y @smithery/cli install @kjozsa/jenkins-mcp --client claude ``` ### Installing Manually ```bash uvx install jenkins-mcp ``` ## Configuration Add the MCP server using the following JSON configuration snippet: ```json { "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: 1. **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 2. **API Token Mode**: Uses Jenkins API tokens which are exempt from CSRF protection - Set `JENKINS_USE_API_TOKEN=true` - Set `JENKINS_PASSWORD` to your API token instead of password - Works 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 ```bash # Install dependencies uv pip install -r …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.