Overview
What is Jenkins Mcp?
Jenkins Mcp is an MCP (Model Context Protocol) server built with Spring AI that wraps the Jenkins REST API, providing a set of common operations for managing Jenkins jobs. It is designed for developers and CI/CD engineers who want to interact with a Jenkins server through an MCP-compliant tool or agent.
How to use Jenkins Mcp?
Clone the repository, run mvn package to build the JAR, then configure your mcp.json with the full path to the JAR and set three environment variables: JENKINS_API_SERVER_URI, JENKINS_API_USERNAME, and JENKINS_API_TOKEN. Launch the server with java -jar <path-to-jar>.
Key features of Jenkins Mcp
- Create, delete, enable, disable, and rename jobs
- Trigger builds with or without parameters
- Stop running builds
- Retrieve job info, build info, and build logs
- Get and update job configuration XML
- Get last build number and timestamp
Use cases of Jenkins Mcp
- Automate CI/CD workflows by creating or modifying Jenkins jobs from an AI agent
- Query build status and logs without logging into the Jenkins UI
- Integrate Jenkins management into a larger MCP-based assistant or toolchain
FAQ from Jenkins Mcp
What technology does Jenkins Mcp use?
It is built with Spring Boot 3.3.6, the Spring AI MCP Server framework, and a Jenkins REST API client.
What are the runtime dependencies?
JDK 17+ and Maven 3.6+ are required to build and run. A Jenkins server with the “Remote Access API” enabled must be accessible.
How is authentication configured?
Set the JENKINS_API_USERNAME and JENKINS_API_TOKEN environment variables in the mcp.json configuration. The token acts as the password.
What operations does Jenkins Mcp support?
It supports job management (create, delete, enable, disable, rename), job building (trigger with or without parameters, stop), job information retrieval (info, build details, logs, last build number/timestamp), and job configuration (get and update XML).
Does Jenkins Mcp store any data?
No. It acts as a stateless proxy between the MCP client and the Jenkins REST API; all data lives on the Jenkins server.
