Jenkins MCP Enterprise
The most advanced Jenkins MCP server available - Enterprise debugging, multi-instance management, AI-powered failure analysis, vector search, and configurable diagnostics for complex CI/CD pipelines.
What is Jenkins MCP Enterprise?
Jenkins MCP Enterprise is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to most advanced jenkins mcp server available - enterprise debugging, multi-instance management, ai-powered failure analysis, vector search, and configurable diagnostics for complex ci/cd pipelines.
The most advanced Jenkins MCP server available - Enterprise debugging, multi-instance management, AI-powered failure analysis, vector search, and configurable diagnostics for complex CI/CD pipelines.
This server falls under the Cloud Services category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- The most advanced Jenkins MCP server available - Enterprise
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx jenkins-mcp-enterpriseConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Jenkins MCP Enterprise
Jenkins MCP Enterprise is an advanced Model Context Protocol server for Jenkins that enables AI assistants to manage CI/CD pipelines, diagnose build failures, and navigate complex multi-instance Jenkins environments through natural language. It provides 15 specialized tools covering build triggering, log inspection with ripgrep, downstream pipeline traversal, and AI-assisted failure diagnosis with configurable recommendations. For teams running multiple Jenkins instances or complex multi-stage pipelines, it also supports optional vector-backed semantic search over log chunks via Qdrant, making it possible to find similar failures across recent builds without manually grepping through logs.
Prerequisites
- Python 3.10 or later installed
- Jenkins instance(s) with API access enabled
- Jenkins username and API token (generate under User → Configure → API Token in Jenkins)
- Docker and Docker Compose if using container deployment
- Qdrant instance if enabling optional semantic search over logs
Clone the repository and install from source
Clone the project and install it as an editable Python package. This makes the jenkins_mcp_enterprise command available in your PATH.
git clone https://github.com/Jordan-Jarvis/jenkins-mcp-enterprise
cd jenkins-mcp-enterprise
python3 -m pip install -e .Create the primary server configuration file
Copy the example config and edit it with your Jenkins URL(s), username, and API token. This is the mandatory configuration layer — the server will not start without it.
mkdir -p config
cp config/mcp-config.example.yml config/mcp-config.ymlEdit mcp-config.yml with your Jenkins credentials
Open config/mcp-config.yml and set your Jenkins base URL, username, and API token. For multi-instance setups, add multiple entries under the servers section.
Optionally configure diagnostic overrides
Create a project-local diagnostic config only if you want to tune failure diagnosis behavior. Otherwise the server uses bundled defaults.
cat > config/diagnostic-parameters.yml << 'ENDDIAG'
semantic_search:
min_diagnostic_score: 0.65
max_total_highlights: 4
recommendations:
max_recommendations: 5
ENDDIAGStart the MCP server
Launch the server with a reference to your primary config file. It will be ready to accept connections from your MCP client.
jenkins_mcp_enterprise --config config/mcp-config.ymlAdd to your MCP client configuration
Register the server in your claude_desktop_config.json or equivalent MCP client config file so the AI assistant can connect to it.
Jenkins MCP Enterprise Examples
Client configuration
Add this to ~/.claude_desktop_config.json. Adjust the config path to match your actual setup.
{
"mcpServers": {
"jenkins": {
"command": "jenkins_mcp_enterprise",
"args": ["--config", "/path/to/jenkins-mcp-enterprise/config/mcp-config.yml"]
}
}
}Prompts to try
Pass full Jenkins build URLs so the server can resolve the correct instance. These prompts exercise the key diagnostic and management capabilities.
- "Analyze this failed build: https://jenkins.company.com/job/api-service/456/"
- "Find the root cause in this nested pipeline: https://jenkins.company.com/job/monorepo/job/main/789/"
- "Show me the test failure section from this build: https://jenkins.company.com/job/tests/321/"
- "Find similar authentication failures in recent builds using semantic search"
- "Trigger the api-service build on https://jenkins.company.com and wait for the result"Troubleshooting Jenkins MCP Enterprise
Server starts but returns 'authentication failed' for Jenkins API calls
Verify the username and API token in mcp-config.yml. Generate a fresh API token in Jenkins under User → Configure → API Token. Ensure the user has at least Read and Build permissions on the target jobs.
semantic_search tool is missing from the tool list
semantic_search is only exposed when vector search is enabled in mcp-config.yml. Set disable_vector_search: false and start the local Qdrant stack with ./scripts/start_dev_environment.sh, then restart the server.
diagnose_build_failure returns generic recommendations
Create a project-local diagnostic-parameters.yml (as shown in step 4) to tune scoring thresholds and the number of recommendations. Place it at config/diagnostic-parameters.yml or pass it with --diagnostic-config.
Frequently Asked Questions about Jenkins MCP Enterprise
What is Jenkins MCP Enterprise?
Jenkins MCP Enterprise is a Model Context Protocol (MCP) server that most advanced jenkins mcp server available - enterprise debugging, multi-instance management, ai-powered failure analysis, vector search, and configurable diagnostics for complex ci/cd pipelines. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Jenkins MCP Enterprise?
Follow the installation instructions on the Jenkins MCP Enterprise GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with Jenkins MCP Enterprise?
Jenkins MCP Enterprise works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Jenkins MCP Enterprise free to use?
Yes, Jenkins MCP Enterprise is open source and available under the GPL-3.0 license. You can use it freely in both personal and commercial projects.
Jenkins MCP Enterprise Alternatives — Similar Cloud Services Servers
Looking for alternatives to Jenkins MCP Enterprise? Here are other popular cloud services servers you can use with Claude, Cursor, and VS Code.
Open WebUI
★ 138.2kUser-friendly AI Interface (Supports Ollama, OpenAI API, ...)
Anything LLM
★ 60.4kThe all-in-one AI productivity accelerator. On device and privacy first with no annoying setup or configuration.
LocalAI
★ 46.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
Nacos
★ 33.0kan easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.
Xiaozhi ESP32
★ 26.7k本项目为xiaozhi-esp32提供后端服务，帮助您快速搭建ESP32设备控制服务器。Backend service for xiaozhi-esp32, helps you quickly build an ESP32 device control server.
Gateway
★ 11.8kA blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.
Browse More Cloud Services MCP Servers
Explore all cloud services servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Jenkins MCP Enterprise in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Jenkins MCP Enterprise?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.