The Jenkins Server MCP enables AI assistants to interact with Jenkins CI/CD servers for build management tasks. You can:
Get the status of specific builds
Trigger new builds (with optional parameters)
Retrieve console output/logs for builds
Provides tools for interacting with Jenkins CI/CD servers, allowing users to check build statuses, trigger builds with parameters, and retrieve build logs from Jenkins jobs.
Connects to TP-Link's Jenkins server (sohoci.rd.tp-link.net/jenkins) by default, enabling interaction with TP-Link's continuous integration environment.
Jenkins Server MCP
A Model Context Protocol (MCP) server that provides tools for interacting with Jenkins CI/CD servers. This server enables AI assistants to check build statuses, trigger builds, and retrieve build logs through a standardized interface.
Installation
Clone this repository:
Install dependencies:
Build the project:
Related MCP server: MCP Toolkit
Configuration
The server requires the following environment variables:
JENKINS_URL: The URL of your Jenkins server (defaults to 'http://sohoci.rd.tp-link.net/jenkins')JENKINS_USER: Jenkins username for authenticationJENKINS_TOKEN: Jenkins API token for authentication
Configure these in your MCP settings file:
For Claude Desktop
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
Tools and Usage
1. Get Build Status
Get the status of a Jenkins build:
Input Schema:
2. Trigger Build
Trigger a new Jenkins build with parameters:
Input Schema:
3. Get Build Log
Retrieve the console output of a Jenkins build:
Input Schema:
Development
For development with auto-rebuild:
Debugging
Since MCP servers communicate over stdio, you can use the MCP Inspector for debugging:
This will provide a URL to access debugging tools in your browser.
License
This project is licensed under the MIT License - see the LICENSE file for details.