Connect your AI assistant to Jenkins. Trigger builds, inspect pipelines, manage jobs — all via natural language.
npx --yes @kud/mcp-jenkins@latest
Comprehensive Jenkins API coverage, flexible auth, and native MCP protocol support for any AI assistant.
No installation required. Add the server to your AI assistant with a single command.
# Via environment variables (recommended) claude mcp add --transport stdio --scope user jenkins \ --env MCP_JENKINS_URL=https://your-jenkins.com \ --env MCP_JENKINS_USER=your_username \ --env MCP_JENKINS_API_TOKEN=your_token \ -- npx --yes @kud/mcp-jenkins@latest # Or via CLI args (override env vars) claude mcp add --transport stdio --scope user jenkins \ -- npx --yes @kud/mcp-jenkins@latest \ --url https://your-jenkins.com \ --user your_username \ --api-token your_token
// claude_desktop_config.json — env vars (recommended)
{
"mcpServers": {
"jenkins": {
"command": "npx",
"args": ["--yes", "@kud/mcp-jenkins@latest"],
"env": {
"MCP_JENKINS_URL": "https://your-jenkins.com",
"MCP_JENKINS_USER": "your_username",
"MCP_JENKINS_API_TOKEN": "your_token"
}
}
}
}
You: List all my Jenkins jobs AI: Found 12 jobs: api-backend, mobile-pipeline, deploy-staging... You: What's the status of the mobile-pipeline build? AI: Build #142 — FAILED in 4m 32s. Stage "Run Tests" failed. You: Show me the console log for that build AI: [2024-01-15 10:23:41] ERROR: 3 tests failed in AuthServiceTest... You: Trigger a new build for deploy-staging with VERSION=2.1.0 AI: Build #67 queued for deploy-staging with VERSION=2.1.0.
From triggering builds to inspecting nodes, every major Jenkins operation is covered.
CLI arguments take priority over environment variables. Use
MCP_JENKINS_* prefixed vars for
env-based config.
| Variable | Description | Example |
|---|---|---|
| MCP_JENKINS_URL | Jenkins server URL (required) | https://jenkins.example.com |
| MCP_JENKINS_USER | Username for Basic auth | admin |
| MCP_JENKINS_API_TOKEN | API token for Basic auth | 11abc...ef |
| MCP_JENKINS_BEARER_TOKEN | Bearer token (OAuth / token auth) | eyJhbGci... |
| MCP_JENKINS_INSTANCES | Comma-separated instance names (multi-instance) | ci,prod |
| MCP_JENKINS_TOOLS | Allowlist — only expose these tools | jenkins_list_jobs,jenkins_get_job_status |
| MCP_JENKINS_BLOCK_TOOLS | Blocklist — hide these tools from the AI | jenkins_delete_job,jenkins_safe_restart |
# Comma-separated values — positional, one per instance MCP_JENKINS_URL=https://pipeline.yourcompany.com,https://scheduler.yourcompany.com MCP_JENKINS_USER=admin,admin MCP_JENKINS_API_TOKEN=token1,token2 # Instances named "pipeline" and "scheduler" from hostnames # Or name them explicitly with MCP_JENKINS_INSTANCES MCP_JENKINS_INSTANCES=ci,prod MCP_JENKINS_URL=https://jenkins.yourcompany.com/ci,https://jenkins.yourcompany.com/prod MCP_JENKINS_USER=admin,admin MCP_JENKINS_API_TOKEN=token1,token2
# Block all write/destructive tools — safe for monitoring dashboards MCP_JENKINS_BLOCK_TOOLS=jenkins_trigger_build,jenkins_stop_build,jenkins_delete_build,\ jenkins_cancel_queue,jenkins_enable_job,jenkins_disable_job,jenkins_delete_job,\ jenkins_create_job,jenkins_update_job_config,jenkins_rename_job,jenkins_copy_job,\ jenkins_toggle_node_offline,jenkins_quiet_down,jenkins_cancel_quiet_down,\ jenkins_safe_restart,jenkins_replay_build