jenkins-mcp-enterprise

# Jenkins MCP Server Enterprise > Jenkins MCP server for multi-instance routing, build diagnostics, and optional vector search. A Model Context Protocol (MCP) server for Jenkins that provides build management, log inspection, failure diagnostics, and multi-instance configuration. The maintained setup paths in this repository are source install and Docker/Compose. ## What It Does - Trigger builds synchronously or asynchronously - Find jobs before triggering or inspecting them - Inspect job definitions and source locations - Retrieve logs and run targeted log-search tools - Discover downstream and sub-build hierarchies - Inspect recent builds or a window around a specific build - Diagnose build failures with configurable recommendations - Route each tool call to the correct Jenkins instance based on `jenkins_url` - Expose `semantic_search` only when vector search is enabled - Expose `apply_job_edit` only when server-side job editing is enabled ## Quick Start ### Prerequisites - Python 3.10+ - Jenkins API access - Jenkins username and API token - Docker and Docker Compose if you want container deployment - Qdrant if you want `semantic_search` ### Install from Source ```bash git clone https://github.com/Jordan-Jarvis/jenkins-mcp-enterprise cd jenkins-mcp-enterprise python3 -m pip install -e . ``` ### Understand the Two Config Layers The server uses two configuration layers: - Primary server config: `config/mcp-config.yml` - Diagnostic config: loaded from one of: - `--diagnostic-config /path/to/file.yml` - `JENKINS_MCP_DIAGNOSTIC_CONFIG=/path/to/file.yml` - `config/diagnostic-parameters.yml` - bundled defaults in `jenkins_mcp_enterprise/diagnostic_config/diagnostic-parameters.yml` You always need the primary server config. You only need a project-local diagnostic config file if you want to override the bundled diagnostic defaults. ### Create the Primary Server Config ```bash mkdir -p config cp config/mcp-config.example.yml config/mcp-config.yml ``…