Jenkins

MCP server from hekmon8/Jenkins-server-mcp

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio hekmon8-jenkins-server-mcp node /path/to/jenkins-server-mcp/build/index.js \
  --env JENKINS_URL="" \
  --env JENKINS_USER="" \
  --env JENKINS_TOKEN=""

How to use

This Jenkins MCP server provides a standardized interface to interact with a Jenkins CI/CD server. It exposes tools to check the status of builds, trigger new builds with specified parameters, and fetch build logs. You can integrate these capabilities into AI assistants or workflows to automate CI tasks without direct Jenkins API calls. The server runs as a Node.js process and is configured via environment variables that point to your Jenkins instance and credentials.

To use it, start the MCP server and connect your client (e.g., Claude or another MCP consumer) to call the available tools. The main tools are: get_build_status to query a specific job's build status, trigger_build to start a build with optional parameters, and get_build_log to retrieve the console output for a given build. Each tool requires a job path and the appropriate metadata (like build number or parameters).

How to install

Prerequisites:

Node.js and npm installed on your system
Access to the repository (clone it)

Installation steps:

Clone the repository: git clone https://github.com/hekmon8/jenkins-server-mcp.git cd jenkins-server-mcp
Install dependencies: npm install
Build the project (if a build step exists): npm run build
Run the MCP server (example): node build/index.js

or use your preferred startup method

Configuration before first run:

Set environment variables for Jenkins access (JENKINS_URL, JENKINS_USER, JENKINS_TOKEN) in your MCP hosting environment or in your Claude/desktop config as shown in the README.

Optional: If you’re integrating with Claude Desktop, place the configuration in your claude_desktop_config.json as demonstrated in the README.

Additional notes

Environment variables:

JENKINS_URL: URL of the Jenkins server (e.g., https://jenkins.example.com)
JENKINS_USER: Jenkins username
JENKINS_TOKEN: Jenkins API token

Common issues:

Ensure the Jenkins API token has the necessary permissions to read job status and trigger builds
If builds require parameters, ensure parameter names exactly match those configured in Jenkins jobs
When running behind proxies or firewalls, configure network access for the MCP server

Tips:

Use lastBuild to refer to the most recent build when querying status or logs
For long-running builds, consider streaming or paginating logs if supported by the client

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.