From the running build to its console output, test report and artifacts, the chase stays in one session — and get_build_console_output takes a pattern with offset and limit, so you can ask for the stack trace instead of the whole log. The plugin tools cover the other half of owning a Jenkins: what is broken, what has an update waiting, and what still has a backupVersion to roll back to.
A Jenkins client in 33 tools covering builds, jobs and folders, agents, plugins, the queue, views, and a Groovy escape hatch for the parts Jenkins does not expose over REST.
- Build inspection: what is running now, a specific build's info, its parameters, its scripts, its test report, and console output paged with offset, limit and a pattern
- Artifacts listed, downloaded — binaries base64-encoded, text as plain text — or handed back as a direct URL
- Jobs triggered and stopped, and items queried by fullname, class or colour pattern down to a folder depth
- A job's parameter definitions read before you trigger it, and job or node configuration read and written as config XML
- Agents listed and inspected, including their executors
- Plugin health: everything installed, the ones with problems, the ones with updates, the ones holding a backupVersion that can be rolled back, and a Graphviz dependency graph for one plugin
- The queue listed, a queue item read by id, and a queued item cancelled
- Views listed and walked by path through nested sub-views, and an arbitrary Groovy script executed on the server
A reachable Jenkins instance and an account on it, plus uv on your PATH, which resolves the Python runtime through UV_PYTHON. run_groovy_script executes arbitrary Groovy on that instance.
One command — uvx mcp-jenkins