Jenkins MCP Server

Production-ready Jenkins Model Context Protocol server for Hermes Agent and other MCP clients.

Tools

23 tools, grouped as the guardrail policy groups them.

Group	Tool	Purpose
@read	list_jobs	List jobs, optionally within a folder
@read	get_job	Job details and recent builds
@read	get_job_config	Fetch config.xml
@read	get_build_info	Build result, duration, parameters
@read	get_build_console	Progressive, size-bounded console log
@read	list_running_builds	Builds currently executing
@read	get_queue	Inspect the build queue
@read	list_nodes	List agents
@read	get_node	Agent details
@write	create_job_from_xml	Create a job from config.xml
@write	create_pipeline_job	Create a Pipeline job
@write	create_multibranch_pipeline	Create a Git multibranch Pipeline
@write	scan_multibranch_pipeline	Trigger a branch scan
@write	copy_job	Copy an existing job
@write	enable_job	Enable a job
@write	disable_job	Disable a job
@write	trigger_build	Trigger a build, with parameters
@destructive	update_job_config	Overwrite an existing config.xml
@destructive	delete_job	Delete a job — irreversible, opt-in
@destructive	stop_build	Stop, terminate, or kill a running build
@destructive	cancel_queue_item	Cancel a queued item
@destructive	set_node_offline	Take an agent offline or online
@admin	jenkins_admin_request	Generic Jenkins REST call — disabled by default

See Security and guardrails for how to restrict these at either layer.

Jenkins compatibility

Jenkins	Line	Status	Coverage
2.555.x	Current LTS	✅ Verified	Full tool suite, every change
2.541.3	LTS	✅ Verified	Full tool suite
2.504.3	LTS 2.504	✅ Verified	Full tool suite
2.504.1	LTS 2.504	✅ Verified	Full tool suite, pinned plugin set
Other 2.x	—	⚪ Supported	Not covered by CI
1.x	—	❌ Unsupported	Different URL scheme, no folders

"Verified" means the full end-to-end suite ran against that core in CI: create a Pipeline job, trigger it, stream the console, stop the build, delete the job, with all 23 tools reachable. Reproduce any row with compatibility.yml.

Run the current LTS line where possible: it is the only line receiving security backports.

Requirements

Authentication	Username and API token. Do not use the account password
Folder paths such as AI/nightly	cloudbees-folder
Pipeline tools, and term/kill on stop_build	workflow-aggregator
Multibranch tools	workflow-multibranch, branch-api, git

A missing plugin disables the tools that depend on it. The rest, including all freestyle and node tools, continue to work on a core-only controller.

Known issues

Symptom	Cause	Fix
Reads succeed, every write returns 403	Strict Crumb Issuer with check client IP; the crumb is bound to a source address that changes behind SNAT or an egress proxy	Disable the IP check, or exclude the MCP server
get_job_config fails, everything else works	The account has Job/Read but not Job/ExtendedRead	Grant Job/ExtendedRead
trigger_build rejected on a parameterised job	Triggered without parameters	Pass parameters, an empty object is enough