Which integrations are available for this server?

Allows inspection of builds, control of jobs, and management of pipeline configuration on a Jenkins CI server, including fetching build status, logs, test reports, triggering and stopping builds, and reading/updating job configuration.

How do I use jenkins-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@jenkins-mcp show me the last 5 builds of the main branch" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

jenkins-mcp

by stubbedev

Overview Schema Related Servers Score Discussions

Remote

jenkins-mcp

A Model Context Protocol (MCP) server for Jenkins, written in Go. Inspect builds, control jobs, and manage pipeline configuration — designed to pair with atlassian-mcp so you can ask "did the build pass?" alongside Jira and Bitbucket questions.

Distributed three ways — all from the same source: a zero-Node prebuilt binary (go install or a release download), an npm wrapper (npx @stubbedev/jenkins-mcp) that fetches the matching binary so every config below works unchanged, and a Nix flake (nix run github:stubbedev/jenkins-mcp).

Tools

Inspection

Tool	Description
`jenkins_get_build`	Status of a build by number, by SHA (auto-finds the build for a commit), or the latest. Includes Pipeline stage breakdown, parameters, changeset, and artifact URLs.
`jenkins_get_log`	Console log for a build. Pass `stageId` for just one Pipeline stage; defaults to a 200KB tail (use `full=true` to opt in to the entire log).
`jenkins_get_tests`	Test report — failing test names, classes, and stack traces. Far more useful than grepping the console log when a build fails.
`jenkins_list_builds`	Recent builds for a job, with result + duration + commit.
`jenkins_list_jobs`	Browse jobs at the root or inside a folder.
`jenkins_get_queue`	Items currently waiting in the build queue.

Build control

Tool	Description
`jenkins_trigger_build`	Trigger a new build, optionally with parameters. Returns a queue item URL to track progress.
`jenkins_stop_build`	Abort a running build by number.

Job configuration

Tool	Description
`jenkins_get_job_config`	Fetch a job's configuration as a structured object (TOON by default) — pipeline definition, triggers, parameters, and retention settings.
`jenkins_update_job_config`	Patch a job's configuration. Pass only the fields to change; everything else is preserved. Supports description, pipeline script/path, triggers, parameters, and build retention.

Natural-language examples

"did CI pass for this commit?" → jenkins_get_build with sha=<HEAD>
"why did build #42 fail?" → jenkins_get_tests (failing tests + stack traces) or jenkins_get_log with stageId=<id> for the failing Pipeline stage
"show me the last 10 builds of master" → jenkins_list_builds
"what jobs exist under platform/api?" → jenkins_list_jobs with folder=platform/api
"what's waiting in the queue?" → jenkins_get_queue
"trigger a build with ENV=production" → jenkins_trigger_build with parameters
"stop the current build" → jenkins_stop_build with buildNumber
"add a nightly cron trigger to this job" → jenkins_get_job_config then jenkins_update_job_config with updated triggers

Related MCP server: Jenkins MCP Server

Setup

1. Generate a Jenkins API token

In Jenkins, click your username (top-right) → Configure.
In the API Token section, click Add new token, give it a name, and click Generate.
Copy the token value — it is only shown once.

2. Create a config file

Create ~/.jenkins-mcp.json:

{
  "$schema": "https://raw.githubusercontent.com/stubbedev/jenkins-mcp/master/jenkins-mcp.schema.json",
  "url": "https://jenkins.example.com",
  "username": "your-jenkins-login",
  "token": "your-api-token",
  "repoJobMap": {
    "stubbedev/atlassian-mcp": "atlassian-mcp/master",
    "kontainer/api": ["kontainer-api/master", "kontainer-api/PR-builds"]
  }
}

The $schema field is optional but enables editor autocomplete and validation.

repoJobMap keys are matched as case-insensitive substrings against the git remote URL of the current repo, so the server can resolve jobPath automatically when you call jenkins_get_build from inside a repo. Values can be a single job path or an array. Job paths use slashes for nested folders (e.g. folder/sub-folder/job-name).

Alternatively, use environment variables (or a .env file in this directory):

JENKINS_URL=https://jenkins.example.com
JENKINS_USERNAME=your-jenkins-login
JENKINS_TOKEN=your-api-token

Config is resolved in this order: --config <path> CLI arg → JENKINS_MCP_CONFIG env var → ~/.jenkins-mcp.json → $XDG_CONFIG_HOME/jenkins-mcp/config.json (default ~/.config/jenkins-mcp/config.json) → .jenkins-mcp.json in cwd → environment variables.

3. Connect to your AI tool

No cloning or building required — point your tool at npx @stubbedev/jenkins-mcp@latest and it will install and run automatically.

Claude Code

claude mcp add jenkins -- npx -y @stubbedev/jenkins-mcp@latest --config ~/.jenkins-mcp.json

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-only):

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["-y", "@stubbedev/jenkins-mcp@latest", "--config", "/Users/you/.jenkins-mcp.json"]
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["-y", "@stubbedev/jenkins-mcp@latest", "--config", "/Users/you/.jenkins-mcp.json"]
    }
  }
}

Zed

Add to ~/.config/zed/settings.json:

{
  "context_servers": {
    "jenkins": {
      "command": {
        "path": "npx",
        "args": ["-y", "@stubbedev/jenkins-mcp@latest", "--config", "/home/you/.jenkins-mcp.json"]
      }
    }
  }
}

OpenCode

Add to opencode.json in your project root (or ~/.config/opencode/opencode.json for global):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jenkins": {
      "type": "local",
      "command": ["npx", "-y", "@stubbedev/jenkins-mcp@latest", "--config", "/home/you/.jenkins-mcp.json"]
    }
  }
}

Codex CLI

Add to ~/.codex/config.yaml:

mcpServers:
  jenkins:
    command: npx
    args:
      - -y
      - @stubbedev/jenkins-mcp@latest
      - --config
      - /home/you/.jenkins-mcp.json

Go install (no Node)

If you have Go installed and prefer a native binary on your PATH:

go install github.com/stubbedev/jenkins-mcp@latest

Then point your MCP client at the jenkins-mcp command directly, e.g. for Claude Code:

claude mcp add jenkins -- jenkins-mcp --config ~/.jenkins-mcp.json

Prebuilt binaries for every platform are also attached to each GitHub release if you'd rather not build.

Nix (NixOS / nix-darwin / home-manager)

Run it straight from the flake — no clone, no install:

nix run github:stubbedev/jenkins-mcp -- --config ~/.jenkins-mcp.json

Or reference it in your MCP client config with that command, or add the flake as an input and use packages.default in your system/home configuration. The flake builds from source with buildGoModule; its version tracks package.json automatically and CI keeps the vendorHash current.

Any other MCP-compatible tool

Most tools that support MCP accept the same JSON format. Use npx as the command with ["-y", "@stubbedev/jenkins-mcp@latest", "--config", "/path/to/config.json"] as the args — or the jenkins-mcp binary directly.

Updating existing installs

If your MCP client is already configured and you want the newest package version:

npx clear-npx-cache

Then restart your MCP client.

Manual install (optional)

If you prefer to clone and build locally (requires Go 1.26+):

git clone git@github.com:stubbedev/jenkins-mcp.git
cd jenkins-mcp
go build -o jenkins-mcp .

Then use /path/to/jenkins-mcp/jenkins-mcp instead of the npx command in the configs above.

Output format (TOON)

Structured tool responses (jenkins_get_job_config, and the config echoed back by jenkins_update_job_config) are serialized as TOON (Token-Oriented Object Notation) by default — a compact, LLM-friendly format that uses fewer tokens than equivalent JSON. Pass format: "json" on those tools to get JSON instead, or set JENKINS_MCP_FORMAT=json to flip the default process-wide. The build/log/test/queue tools already return purpose-built plain text and are unaffected.

Transport: stdio (default) or HTTP

By default the server speaks MCP over stdio — the right choice when your AI tool launches the binary as a child process (the configs above).

To run it as a long-lived service — e.g. shared by a team, or sitting behind a reverse proxy — start it in Streamable HTTP mode instead:

jenkins-mcp --http                 # listen on 127.0.0.1:8080/mcp
jenkins-mcp --http 0.0.0.0:9000    # bind a specific addr/port
JENKINS_MCP_HTTP=:8080 jenkins-mcp # same, via env (handy in containers)

Flag / env	Effect
`--http[=addr]` / `--http addr`	Enable HTTP. `addr` defaults to `127.0.0.1:8080`.
`JENKINS_MCP_HTTP=addr`	Enable HTTP via env. `1`/`true` means the default addr.
`JENKINS_MCP_HTTP_PATH=/path`	Endpoint path (default `/mcp`).
`--http-stateless` / `JENKINS_MCP_HTTP_STATELESS=1`	Drop persistent sessions (see below).

Point your MCP client at http://<host>:<port>/mcp. Put TLS/auth on the proxy in front; the server itself does not terminate TLS.

The HTTP server is stateful by default: it keeps a session per client so server→client requests work — namely the MCP roots lookup used to find the caller's repo, and the elicitation prompt that disambiguates when a repo maps to multiple Jenkins jobs. This is the right default for a local proxy (single tenant — nothing to load-balance).

If you front it with a cloud load balancer, pass --http-stateless: every request becomes self-contained with no session affinity to pin. The trade-off is that roots resolution and the elicitation picker no longer work — supply the repo root via header/arg and pass jobPath explicitly.

Working directory in HTTP mode

In stdio mode the server runs git in its own working directory to auto-resolve jobPath from the current repo's remote (via repoJobMap). Over HTTP there is no single working tree — the process serves many callers — so the working tree is resolved per request, checked in this order:

cwd (or repoRoot) tool argument — supply the repo root on the call; git runs there for that request.
X-Repo-Root (or X-Cwd) HTTP header — a fronting proxy/harness can inject the repo root per request.
MCP roots — if the client exposes its workspace via the roots capability, git runs there. With several roots, the server runs git in each and unions the repoJobMap matches, so the one root that maps to a Jenkins job wins automatically; if several roots map to different jobs you get the elicitation picker. Cached per session and refreshed on roots/list_changed (stateful mode only).

If none of these yields a repo (e.g. stateless mode with no header, or no root maps), pass jobPath explicitly. Errors name the resolved directory (e.g. "ran git in /x but found no origin remote") so misconfiguration is obvious.

Operational notes (HTTP)

Health check: GET /healthz returns 200 ok jenkins-mcp <version> — wire it to your proxy/orchestrator liveness probe.
Graceful shutdown: SIGINT/SIGTERM drains in-flight requests (5s) before exiting.
Session reaping: stateful sessions idle longer than 30 min are dropped, so a long-lived server doesn't leak state from clients that disconnected uncleanly.
No hangs: git invocations run with GIT_TERMINAL_PROMPT=0 and a 10s timeout; the roots/list lookup has a 5s timeout. A wedged client or repo can't stall a tool call.

Notes

Authentication is HTTP Basic with username:apitoken (Jenkins's standard mechanism).
Write operations (jenkins_trigger_build, jenkins_stop_build, jenkins_update_job_config) require the API token user to have the appropriate Jenkins permissions.
CSRF crumb handling is automatic — API tokens bypass the crumb check on most Jenkins installations, but the server fetches and caches a crumb for installations that require it.
jenkins_get_build with sha scans the last 30 builds of the job for a matching lastBuiltRevision. Increase scanLimit for repos with many builds per commit.
Pipeline stage breakdown comes from Jenkins's wfapi (workflow plugin). Freestyle jobs don't expose it, and the tool falls back to summary fields only.
Test reports come from the standard Jenkins JUnit / xUnit plugins. Jobs that don't publish results return a friendly 404 message.

Releases (Maintainers)

Each release ships both prebuilt Go binaries (attached to the GitHub release) and the npm wrapper @stubbedev/jenkins-mcp. .github/workflows/publish.yml runs on a pushed v* tag and: cross-compiles binaries for 14 targets — linux (amd64, arm64, arm/v7, 386, ppc64le, s390x, riscv64), darwin (amd64, arm64), windows (amd64, arm64, 386), and freebsd (amd64, arm64) — attaches them to the GitHub release, then publishes the npm package. The Nix flake builds from the tagged source and tracks package.json for its version, so it needs no separate release step.

Use semantic versioning. Breaking tool-surface changes should bump the minor version while <1.0.0 (for example 0.0.x -> 0.1.0).

Release flow (the preversion hook runs go vet, go test, and the smoke check first):

# choose one: patch | minor | major
npm run release:minor

This bumps package.json, commits, tags, and pushes; the pushed tag drives the publish workflow.

The npm step uses npm Trusted Publisher (OIDC), so no NPM_TOKEN secret is required
The release step uses the default GITHUB_TOKEN

Required npm setup (one-time):

In npm package settings, add this GitHub repo/workflow as a Trusted Publisher

Development

Requires Go 1.26+. Dependencies: modelcontextprotocol/go-sdk (official MCP SDK), toon-format/toon-go (TOON output), and beevik/etree (lossless config.xml editing).

# Build
go build -o jenkins-mcp .

# Run directly
./jenkins-mcp --config /path/to/config.json

# Vet + test
go vet ./...
go test ./...

# Quick smoke check (builds + validates tools/list)
npm run smoke

# Test the tool list by hand
printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' | ./jenkins-mcp

Tool schemas live in tools.json (embedded into the binary via go:embed). The npm wrapper lives in bin/cli.mjs + scripts/. The Nix flake is flake.nix.

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

1wRelease cycle

7Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stubbedev/jenkins-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server