Labsco
MCP SERVER

Jenkins MCP Server

by NithishNithi

Trigger a Jenkins build, watch it, read the log and pull the artifact — from the client you are already in.

Build Systems & CI/CD
Summary
The build is triggered and diagnosed in one place.

The log and the artifact sit on the same connection as the trigger, so 'run it and tell me why it failed' does not become three browser tabs. Prefixed tool names let a prod and a staging Jenkins be connected at the same time.

What it is

A Go MCP server over the Jenkins REST API. It covers jobs, builds, the queue, logs, artifacts and views, authenticates with a username and API token over TLS, and retries transient failures with exponential backoff.

What you get
  • Jobs and views listed, and one job's detail read
  • A build triggered, running builds watched, and a build stopped
  • A build's status read, and its console log retrieved
  • The queue read, a queue item inspected, and a queued item cancelled
  • A build's artifacts listed and downloaded
  • Tool names prefixed through JENKINS_TOOL_PREFIX, so several Jenkins instances can be connected at once
Requirements

A Jenkins instance plus a username and API token — JENKINS_URL, JENKINS_USERNAME and JENKINS_API_TOKEN, or the same values in config.yaml. A custom CA certificate, timeouts and retry counts are configurable; building from source needs Go 1.23.6 or later.

Setup effort

One command plus a key — go install github.com/NithishNithi/go-jenkins-mcp/cmd/jenkins-mcp-server@latest, then supply credentials