Jenkins MCP MCP Server

English | [中文](README.zh-CN.md) # Jenkins API MCP Server This is a MCP Server service based on Spring AI for Jenkins Rest API calls, providing common

Local serverstdio

What is the Jenkins MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Jenkins MCP MCP server moves it into the conversation instead. English | 中文 # Jenkins API MCP Server This is a MCP Server service based on Spring AI for Jenkins Rest API calls, providing common operation interfaces for Jenkins jobs. ## Features - Job Management: Create, delete.

The short version

  • Job Management: Create, delete, enable/disable, rename jobs
  • Job Building: Trigger builds, build with parameters, stop builds
  • Job Information: Get job info, build info, build logs
  • Job Configuration: Get and update job configurations

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Requirements — The Requirements tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: JENKINS_API_SERVER_URI, JENKINS_API_USERNAME, JENKINS_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • JDK 17+ - Maven 3.6+ - Jenkins server (with "Remote Access API" enabled)

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jenkins MCP's toolset — Requirements — is a fair guide to whether it matches your workflow. It is maintained by ProgrammerAgua; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Jenkins MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
RequirementsThe Requirements tool exposed by this server.

How to install the Jenkins MCP MCP server

### mcp.json Configuration
```yaml
{
  "mcpServers": {
    "jenkins-mcp": {
      "command": "java",
      "args": [
        "-jar",
        "{your_path}\\mcp-jenkins-server-0.0.1-SNAPSHOT.jar"
      ],
      "env": {
        "JENKINS_API_SERVER_URI": "jenkins-uri",
        "JENKINS_API_USERNAME": "username", 
        "JENKINS_API_TOKEN": "password/token"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • JDK 17+ - Maven 3.6+ - Jenkins server (with "Remote Access API" enabled)
VariableDescriptionRequired
JENKINS_API_SERVER_URIConfiguration value read at startup.Optional
JENKINS_API_USERNAMEConfiguration value read at startup.Optional
JENKINS_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Jenkins MCP to Requirements.

Frequently asked questions

It is built with Spring Boot 3.3.6, the Spring AI MCP Server framework, and a Jenkins REST API client.