Claude + Jenkins: What the Integration Can (and Can't) Do in 2026
Yes, with a twist — there’s no Jenkins connector in Claude’s directory, but Jenkins ships an official MCP Server plugin. The MCP Server plugin is maintained under the jenkinsci org — genuinely official Jenkins-project code, not vendor marketing. Install it and your instance exposes an MCP endpoint at <jenkins-url>/mcp-server/mcp, authenticated with your normal Jenkins API token. The reason there’s no one-click directory connector is the same reason setup takes thought: most Jenkins boxes live on private networks, so the realistic clients are Claude Code or Claude Desktop on a machine that can actually reach Jenkins. And the usual Claude ceiling applies: it all runs inside a conversation you start — nothing watches your builds for you.
Here’s what the plugin does, how to wire it up, where the limits bite, and what to use if you want CI work that runs on its own.
What the official Jenkins MCP Server plugin does
The plugin (version 0.178.x, actively updated through mid-2026, requires Jenkins 2.533+) turns your controller into an MCP server. Connected, Claude can:
- List and inspect jobs — browse jobs, check statuses, pull build metadata.
- Trigger builds — including parameterized builds, straight from a chat (“kick off the release job with version 4.2”).
- Fetch and search build logs — pull console output and hunt through it for the failing stage or test.
- Replay Pipeline builds and manage the queue — rerun pipelines, inspect what’s waiting and why.
- Read SCM and changeset info — see which commits landed in a build, useful for “who broke it” archaeology.
- Check instance health — a quick status read on the controller itself.
It speaks streamable HTTP at /mcp-server/mcp (recommended), with /mcp-server/sse and /mcp-server/stateless variants.
How to set it up
- Install the MCP Server plugin from the Jenkins update center (Manage Jenkins → Plugins). You’ll need Jenkins 2.533 or newer.
- Generate an API token for your Jenkins user (Configure → API Token).
- Add
<your-jenkins-url>/mcp-server/mcpto Claude as a custom MCP connector, using the token as an HTTP Basic auth header. In Claude Code this is anmcp addaway; Claude Desktop takes it as a custom connector. - Ask Claude to list jobs or pull a build log — it hits your instance directly.
The network reality: claude.ai in the browser can only reach an MCP endpoint on the public internet, and most Jenkins instances rightly aren’t. Claude Code or Claude Desktop running inside your VPN or office network is the clean path. Tunnels (ngrok, Cloudflare) work but mean exposing your CI — treat that decision with the caution it deserves.
Community alternatives exist too — kud/mcp-jenkins and alexsarrell/jenkins-mcp-server (18 tools, built partly to dodge the official plugin’s 30-second timeout) — but the jenkinsci plugin is the one with official standing.
The limits that actually matter
- No triggers, no monitoring. The MCP server answers when Claude asks. There’s no “when the nightly build fails, summarize the log and ping the committer.” Jenkins core doesn’t even ship outbound webhooks — plugins fill that gap — and Claude has no way to receive one regardless.
- Conversation-only. Claude triages the build you point it at, brilliantly. Close the chat and nothing continues — no watching the queue, no chasing a deploy to green.
- Network-bound. Your Claude client has to reach the instance. That’s fine at your desk on the VPN; it’s nothing at 3am when the pipeline breaks.
- Laptop-bound for anything scheduled. The closest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. Not a CI babysitter.
So Claude is excellent for “why did this build fail, right now, while I’m looking at it” — and not built for “tell me when builds fail and start the cleanup.”
If you want Jenkins work that runs on its own: Carly
Build failures don’t schedule themselves for business hours. The moment you want CI events handled without you in a chat, you’ve crossed past what an MCP server is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers and schedules. Jenkins connects to Carly via your own API token — paste your Jenkins URL and token on carlyassistant.com/integrations — and Carly works Jenkins’ REST API (job status, buildWithParameters, console logs):
- Every morning before standup, Carly checks overnight builds on main; if anything failed, it pulls the console log, summarizes the probable cause, and emails you the digest.
- On a build failure (via a notification-plugin webhook or status polling), Carly greps the tail of the log, identifies the failing stage or test, drafts the ticket, and emails the last committer.
- Deploy windows on a schedule — Friday 4pm, Carly triggers the release job with your version parameter, watches status, and emails stakeholders when it goes green.
- Weekly flaky-job report — jobs with repeat failures, build-duration trends, longest queue waits, in your inbox Monday morning.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
- Actually sends — drafts and sends email across Gmail and Outlook, updates tasks and records.
- Connects to anything — 200+ native integrations (see integrations), plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude’s Jenkins MCP vs Carly
| Claude (Jenkins MCP plugin) | Carly | |
|---|---|---|
| Trigger builds from natural language | Yes | Yes |
| Read and search build logs | Yes | Yes |
| Reacts when a build fails | No | Yes |
| Scheduled build digests | No | Yes |
| Works while your laptop is closed | No (client must reach Jenkins) | Yes (cloud) |
| Emails the committer / stakeholders | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with the MCP plugin is a sharp CI console you talk to. Carly is a teammate that watches the pipeline between your logins.
Frequently Asked Questions
Does Claude work with Jenkins?
Yes — not via a directory connector, but through the official Jenkins MCP Server plugin maintained by the Jenkins project. It exposes an MCP endpoint at <jenkins-url>/mcp-server/mcp (API-token auth), and Claude can list jobs, trigger builds, fetch and search logs, replay pipelines, and check instance health. Because most Jenkins instances are on private networks, Claude Code or Claude Desktop on a machine that can reach the box is the realistic setup.
Can Claude trigger a Jenkins build?
Yes, inside a chat — the MCP plugin exposes build triggering, including parameterized builds. What Claude can’t do is trigger itself: there’s no schedule or event hook, so a human starts every interaction.
Can I use Jenkins with Claude on claude.ai in the browser?
Only if your MCP endpoint is reachable from the public internet, which most Jenkins instances aren’t (and shouldn’t casually be). Use Claude Code or Claude Desktop inside the network or VPN, or accept the security tradeoffs of a tunnel.
Can Claude notify me when a build fails?
No. The MCP server has no outbound path — Claude only acts inside a conversation you start. For failure alerts with a log summary and a drafted ticket, you need a trigger-based agent like Carly, which polls the JSON API or catches a webhook and emails you. AI agents start at $35/month.
More: Claude + GitHub · Claude + GitLab · Claude + CircleCI · Claude + Sentry · Claude connectors · Can Claude send emails
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
