mcp-jenkins
by lanbaoshen·★ 120·Score 47
MCP server for Jenkins integration, providing tools to interact with Jenkins CI/CD through AI assistants.
Overview
The MCP Jenkins server bridges Jenkins CI/CD infrastructure with AI assistants through the Model Context Protocol. It enables secure, contextual interactions with Jenkins tools while maintaining data privacy. The server implements proper authentication via username/password or API tokens and supports multiple transport methods including stdio, SSE, and streamable HTTP. With comprehensive tool coverage for builds, nodes, queue items, and artifacts, it allows AI assistants to perform Jenkins operations seamlessly.
Try asking AI
After installing, here are 7 things you can ask your AI assistant:
When to choose this
Choose this server when your team uses Jenkins for CI/CD and wants AI assistants to manage or query pipeline status, build jobs, and Jenkins resources through natural language.
When NOT to choose this
Don't choose this if you use a different CI/CD system (like GitLab CI, GitHub Actions, or Azure DevOps) as this server is specifically designed for Jenkins integration only.
Tools this server exposes
12 tools extracted from the READMEget_itemGet a specific item by name.
get_item_configGet the configuration of a specific item.
get_all_itemsGet all items in Jenkins.
build_itemBuild a item.
get_buildGet a specific build by job name and build number.
get_build_console_outputGet the console output of a specific build.
stop_buildStop a specific build by job name and build number.
get_all_nodesGet all nodes in Jenkins.
get_queue_itemGet a specific queue item by ID.
cancel_queue_itemCancel a specific queue item by ID.
get_viewGet a specific view by name.
get_all_viewsGet the configuration of a specific view.
Comparable tools
Installation
Installation
Using pip:
pip install mcp-jenkins
mcp-jenkinsUsing uv (recommended):
pip install uv
uvx mcp-jenkinsDocker:
docker pull ghcr.io/lanbaoshen/mcp-jenkins:latest
docker run -p 9887:9887 --rm ghcr.io/lanbaoshen/mcp-jenkins:latest --transport streamable-httpClaude Desktop Configuration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"jenkins": {
"command": "uvx",
"args": ["mcp-jenkins", "--jenkins-url=YOUR_JENKINS_URL", "--jenkins-username=YOUR_USERNAME", "--jenkins-password=YOUR_TOKEN"]
}
}
}FAQ
- How do I authenticate with Jenkins?
- You can authenticate using either a username and password or a Jenkins API token. These can be provided via command line arguments (--jenkins-username, --jenkins-password) or through headers if using the HTTP transport.
- What transport methods are supported?
- The server supports three transport methods: stdio (default), SSE (Server-Sent Events), and streamable HTTP. You can specify your preferred transport using the --transport argument.
- Can I run this in read-only mode?
- Yes, you can enable read-only mode by using the --read-only flag, which will prevent any modifications to Jenkins resources.
Compare mcp-jenkins with
Last updated · Auto-generated from public README + GitHub signals.