Jenkins MCP 서버 멀티 인역 라우팅, 구축 진단 및 옵션 벡터 검색.

빌드 관리, 로그 검사, 실패 진단 및 멀티 인스턴스 구성을 제공하는 Jenkins 용 모델 Context Protocol (MCP) 서버. 이 저장소의 유지 보수 설정 경로는 소스 설치 및 Docker/Compose입니다.

그것은 무엇을

• Trigger는 동시 또는 비동기적으로 만듭니다
• 트리거 또는 검사하기 전에 작업 찾기
• 작업 정의 및 소스 위치를 검사
• 로그를 검색하고 타겟 로그 검색 도구를 실행
• downstream 및 하위 빌드 hierarchies를 발견
• 최근 빌드 또는 특정 빌드 주위에 창 검사
• Diagnose는 configurable 권고를 가진 실패를 건설합니다
• 각 도구는 올바른 Jenkins 인스턴스에 호출합니다. jenkins_url
• semantic_search 벡터 검색이 활성화되면 노출
• Expose apply_job_edit 서버 측 작업 편집이 활성화되면

빠른 시작

# 필수품

• 파이썬 3.10+
• Jenkins API 액세스
• Jenkins 사용자 및 API 토큰
• Container 배포를 원하면 Docker 및 Docker Compose
• 당신이 원하는 경우 Qdrant semantic_search

소스에서 설치

2개의 Config 층의 밑에

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

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

mkdir -p config
cp config/mcp-config.example.yml config/mcp-config.yml

Edit config/mcp-config.yml with your Jenkins URLs and credentials.

If you want the optional Jenkins-managed job edit workflow for non-SCM-backed jobs, also set:

settings:
  enable_job_editing: true
  job_edit_workspace_dir: "/tmp/mcp-jenkins/job-definitions"

Optional Project-Local Diagnostic Override

Create this only if you want to tune diagnose_build_failure:

cat > config/diagnostic-parameters.yml << 'ENDDIAG'
semantic_search:
  min_diagnostic_score: 0.65
  max_total_highlights: 4

recommendations:
  max_recommendations: 5
ENDDIAG

If you want semantic search, start the local vector stack and set disable_vector_search: false with vector.host: "http://localhost:6333":

./scripts/start_dev_environment.sh

Docker and Compose

cp config/mcp-config.example.yml config/mcp-config.yml
./start-jenkins_mcp_enterprise.sh

See README-Docker.md for the container deployment flow.

Start the Server