Creativity · MCP — server
MCP Jenkins Server
Jenkins is the grand old workhorse of CI/CD, still running builds for enterprises everywhere. The MCP Jenkins Server wraps its XML and JSON APIs to let MCP clients list jobs, read build logs, trigger jobs, and inspect pipeline stages — a practical chat interface for long-running Jenkins estates.
MCP facts
- Kind
- server
- Ecosystem
- anthropic-mcp
- Language
- Python
- Transports
- stdio
Capabilities
- Tools: list_jobs, get_build, get_console_log, trigger_build, cancel_build
- API token or basic auth
- Supports Jenkins pipelines and multibranch projects
Install
pip install mcp-jenkins Configuration
{
"mcpServers": {
"jenkins": {
"command": "uvx",
"args": ["mcp-jenkins"],
"env": {
"JENKINS_URL": "https://jenkins.example.com",
"JENKINS_USERNAME": "claude",
"JENKINS_API_TOKEN": "<token>"
}
}
}
} Frequently asked questions
Does it support Blue Ocean pipelines?
Yes — pipeline stages come through the regular API. Blue Ocean's UI is separate, but the underlying data is accessible.
Concerns with long log output?
The server paginates console logs and defaults to the last N kilobytes. Claude can request earlier offsets if needed, but summarizing typically beats streaming.
Trigger safety?
Limit triggerable jobs via Jenkins' role-based strategy and require MCP client approval before trigger_build fires against production pipelines.
Sources
- Jenkins REST API — accessed 2026-04-20
- Model Context Protocol — accessed 2026-04-20