$ loading_
Trigger, monitor, and inspect Jenkins jobs and build logs via MCP.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Jenkins MCP Proxy" yet — see the docs or source repo.
Use Jenkins MCP Proxy to trigger the Jenkins job named production-deploy with branch set to main and environment set to prod, then return the queue status and build number.
Confirmation that the job was triggered, along with queue status and the resulting build number.
Check the latest build of the Jenkins job backend-ci, including status, start time, duration, and failed stage; if it failed, summarize possible causes.
A concise report of the latest build status, including failed stages and a summary of likely causes.
Retrieve the console log for build #245 of the Jenkins job frontend-test, extract the error messages, and list recommended troubleshooting steps by priority.
Key error excerpts from the log, plus an actionable prioritized troubleshooting checklist.
Connect to Jenkins via MCP to manage jobs, pipelines, and artifacts.
Securely query Jenkins builds, logs, artifacts, and generate verification reports.
Query and control Jenkins jobs, builds, nodes, and queues using natural language.
Manage Jenkins jobs, trigger builds, and fetch logs using natural language.
Proxy MCP to JSON-RPC for AI-driven 1C task, project, knowledge, and file management.
Proxy multiple MCP servers while reducing token usage with on-demand tool loading.