Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Jenkins to Claude Code

Let Claude trigger builds and manage jobs in Jenkins. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Jenkins to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Jenkins, you add a Jenkins MCP server: a small hosted service that exposes Jenkins's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Jenkins account. No API keys pasted into config files.

claude mcp add --transport http jenkins https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Jenkins once connected?

Full read-write Jenkins access lets Claude trigger a parameterized build, enable or disable a job, retry a failed pipeline stage, and queue deploys once you approve. The pipeline work that used to mean switching to the Jenkins dashboard happens where you are already discussing the change.

  • Trigger a parameterized build for a specific job and branch
  • Enable or disable a job to pause or resume its pipeline
  • Retry or re-run a failed build after you approve
  • Cancel a queued or running build that is no longer needed
  • Create or update a job from a config you confirm
  • Promote a completed build with the Promoted Builds plugin once you approve

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Jenkins access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Jenkins API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Jenkins changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Jenkins connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Jenkins connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Jenkins account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Jenkins's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Jenkins?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Jenkins account it signs in with. Revoking access is one click in Jenkins.

More on the Jenkins connector

Jenkins connector for claude.aiBitbucket + Claude CodeCircleCI + Claude CodeVercel + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us