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.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Jenkins Server MCP check the status of the last build for view/xxx_debug"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Website | Description |
Free AI SaaS Product Directory & Listing Platform - Submit your AI products and SaaS tools for free exposure and discovery | |
Free AI Tools & SaaS Directory for Developers - Discover and list innovative AI-powered tools and SaaS applications | |
Free AI-Powered Image Merging & Combination Tool - Merge and combine multiple images effortlessly with AI technology |
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.
Related MCP server: Jenkins MCP Server
Clone this repository:
git clone https://github.com/hekmon8/jenkins-server-mcp.git
cd jenkins-server-mcpInstall dependencies:
npm installBuild the project:
npm run buildThe server requires the following environment variables:
JENKINS_URL: The URL of your Jenkins server
JENKINS_USER: Jenkins username for authentication
JENKINS_TOKEN: Jenkins API token for authentication
Configure these in your MCP settings file:
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"jenkins-server": {
"command": "node",
"args": ["/path/to/jenkins-server-mcp/build/index.js"],
"env": {
"JENKINS_URL": "https://your-jenkins-server.com",
"JENKINS_USER": "your-username",
"JENKINS_TOKEN": "your-api-token"
}
}
}
}Get the status of a Jenkins build:
// Example usage
const result = await mcpClient.useTool("jenkins-server", "get_build_status", {
jobPath: "view/xxx_debug",
buildNumber: "lastBuild" // Optional, defaults to lastBuild
});Input Schema:
{
"jobPath": "string", // Relative Jenkins job path (must not start with "/", "\\", or include a URL scheme)
"buildNumber": "string" // Optional, build number or "lastBuild"
}Trigger a new Jenkins build with parameters:
// Example usage
const result = await mcpClient.useTool("jenkins-server", "trigger_build", {
jobPath: "view/xxx_debug",
parameters: {
BRANCH: "main",
BUILD_TYPE: "debug"
}
});Input Schema:
{
"jobPath": "string", // Relative Jenkins job path (must not start with "/", "\\", or include a URL scheme)
"parameters": {
// Build parameters as key-value pairs
}
}Retrieve the console output of a Jenkins build:
// Example usage
const result = await mcpClient.useTool("jenkins-server", "get_build_log", {
jobPath: "view/xxx_debug",
buildNumber: "lastBuild"
});Input Schema:
{
"jobPath": "string", // Relative Jenkins job path (must not start with "/", "\\", or include a URL scheme)
"buildNumber": "string" // Build number or "lastBuild"
}For development with auto-rebuild:
npm run watchSince MCP servers communicate over stdio, you can use the MCP Inspector for debugging:
npm run inspectorThis will provide a URL to access debugging tools in your browser.
Thanks AIMCP(https://www.aimcp.info).
This project is licensed under the MIT License - see the LICENSE file for details.
Get the console output of a Jenkins build
Inputs: buildNumber (required), jobPath (required).
Get the status of a Jenkins build
Inputs: jobPath (required), buildNumber.
Trigger a new Jenkins build
Inputs: jobPath (required), parameters (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clearly distinct purpose: get_build_log retrieves console output, get_build_status checks build status, and trigger_build initiates new builds. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern (get_build_log, get_build_status, trigger_build) with clear, descriptive names. The naming convention is uniform and predictable throughout the set.
With only 3 tools, the server feels thin for a Jenkins integration, which typically involves more operations like managing jobs, viewing queue status, or canceling builds. While the tools cover basic build interactions, the scope is limited.
The toolset is severely incomplete for Jenkins functionality. It lacks core operations such as listing jobs, viewing build history, managing job configurations, or handling Jenkins system information. Agents will face significant gaps in performing typical Jenkins tasks.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Buildkite MCP server exposes Buildkite product data (pipelines, builds, jobs, and test data) to AI tools, editors, and agents through the Model Context Protocol. It provides capabilities including pipeline creation and management, build monitoring with specialized tools like 'wait_for_build', efficient log querying using Apache Parquet conversion and caching, and OAuth-based authentication for both read-write and read-only access to Buildkite's REST API.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
A Model Context Protocol server for Wix AI tools
