Jenkins CLI + MCP server — build lifecycle, pipelines, logs, artifacts, queue, credentials, plugins, multi-context, node/user admin, and a native MCP server for AI agents
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":"jenkins-mcp-cli","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://github.com/ml-lubich/jenkins-mcp/actions/workflows/ci.yml) A Jenkins CLI + MCP server — build lifecycle with exit codes, pipeline/stage inspection, live logs, input steps, artifacts, queue management, credentials, plugins, multi-context profiles, and node/user/git-tool administration, from the terminal or from AI agents. Pure standard library (argparse + urllib + json) — no extra runtime dependencies beyond the `mcp` package needed for `serve`. ```bash jenkins-mcp status jenkins-mcp job build my-pipeline --watch -p BRANCH=main jenkins-mcp job log my-pipeline -f jenkins-mcp pipeline info my-pipeline jenkins-mcp doctor jenkins-mcp serve ``` ## Why jenkins-mcp Compared to other Jenkins CLIs (e.g. `addozhang/jk`, the `jk` community skill), `jenkins-mcp` is a superset: everything they do, plus Jenkins administration and a native MCP server. | Capability | jenkins-mcp | jk | |---|---|---| | Build lifecycle with `--watch` exit codes (0/1/2/3/4/10) | ✅ | ✅ | | Live/follow console logs (`job log -f`) | ✅ | ✅ | | Pipeline stage tree (`pipeline info`) | ✅ | ✅ | | Pipeline input steps (`build input`) | ✅ | ✅ | | Build artifacts list/download | ✅ | ✅ | | Build queue list/cancel | ✅ | ✅ | | Build rerun/replay with same parameters | ✅ | ✅ | | `doctor` connectivity/auth/version checks | ✅ | ✅ | | Fuzzy job name search | ✅ | ✅ | | Multi-context / named profiles | ✅ | ✅ (URL-as-identity) | | Machine-readable `-o json` output | ✅ | ✅ | | **Node/agent management** (add/remove worker nodes) | ✅ | ❌ | | **User account management** | ✅ | ❌ | | **Credentials management** (create/list/delete) | ✅ | ❌ | | **Plugin management** (list/install) | ✅ | ❌ | | **Native MCP server** for AI agents (`jenkins-mcp serve`) | ✅ | ❌ | `jk` is explicitly scoped to build/pipeline operations and does not manage nodes, users, credentials, or plugins — `jenkins-mcp` covers both the developer workfl…
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.