Jenkins MCP
젠킨스 MCP
Jenkins 작업을 관리하기 위한 MCP 서버입니다.
설치
Smithery를 통해 설치
Smithery를 통해 Claude Desktop에 Jenkins MCP를 자동으로 설치하려면:
지엑스피1
수동 설치
uvx install jenkins-mcpRelated MCP server: jenkins-mcp-server
구성
다음 JSON 구성 스니펫을 사용하여 MCP 서버를 추가합니다.
{
"mcpServers": {
"jenkins-mcp": {
"command": "uvx",
"args": ["jenkins-mcp"],
"env": {
"JENKINS_URL": "https://your-jenkins-server/",
"JENKINS_USERNAME": "your-username",
"JENKINS_PASSWORD": "your-password",
"JENKINS_USE_API_TOKEN": "false"
}
}
}
}CSRF 크럼 처리
Jenkins는 POST 요청에 포함되어야 하는 토큰인 "크럼"을 사용하여 CSRF 보호를 구현합니다. 이 MCP 서버는 두 가지 방식으로 CSRF 크럼을 처리합니다.
기본 모드 : 빌드 요청에 CSRF 크럼을 자동으로 가져와 포함합니다.
웹 세션을 유지하기 위해 세션 쿠키를 사용합니다.
모든 CSRF 보호를 백그라운드에서 처리합니다.
API 토큰 모드 : CSRF 보호에서 면제되는 Jenkins API 토큰을 사용합니다.
JENKINS_USE_API_TOKEN=true설정하세요비밀번호 대신
JENKINS_PASSWORDAPI 토큰으로 설정하세요.API 토큰 인증에 대한 크럼이 필요하지 않은 Jenkins 2.96 이상과 함께 작동합니다.
Jenkins에서 API 토큰을 생성할 수 있습니다: 사용자 → 구성 → API 토큰 → 새 토큰 추가
특징
Jenkins 채용 공고 목록
선택적 매개변수를 사용하여 빌드 트리거
빌드 상태 확인
안전한 API 액세스를 위한 CSRF 크럼 처리
개발
# Install dependencies
uv pip install -r requirements.txt
# Run in dev mode with Inspector
mcp dev jenkins_mcp/server.pyAvailable Tools
3 toolsget_build_statusB
Get build status
Args:
job_name: Name of the job
build_number: Build number to check, defaults to latest
Returns:
Build information dictionary
Inputs: job_name (required), build_number.
list_jobsB
List all Jenkins jobs
Inputs: no named parameters. Returns: result
trigger_buildB
Trigger a Jenkins build
Args:
job_name: Name of the job to build
parameters: Optional build parameters as a dictionary (e.g. {"param1": "value1"})
Returns:
Dictionary containing build information including the build number
Inputs: job_name (required), parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_build_status retrieves status information, list_jobs enumerates available jobs, and trigger_build initiates new builds. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (get_build_status, list_jobs, trigger_build). The verbs are descriptive and appropriate for their actions, and snake_case is used uniformly throughout.
With only 3 tools, the set feels thin for a Jenkins integration, which typically involves more operations like viewing logs, managing job configurations, or canceling builds. This limited scope may hinder agent workflows that require broader control.
The toolset is severely incomplete for Jenkins automation. It lacks essential operations such as viewing build logs, updating job configurations, canceling builds, or managing nodes/plugins. This creates significant gaps that will likely cause agent failures in common use cases.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with a Jenkins CI/CD server. Allows you to trigger jobs, check build statuses, and manage your Jenkins instance through MCP.46 npm14Apache 2.0
- FlicenseAqualityDmaintenanceExposes a Jenkins controller's REST API to MCP-compatible clients, enabling job management, build triggering, and log retrieval through natural language.114-
- AlicenseNot gradedqualityDmaintenanceEnables Jenkins CI/CD integration with job management, pipeline monitoring, artifact handling, and batch operations via MCP.4Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and external systems to programmatically trigger and monitor Jenkins jobs, retrieve build status and logs via MCP standards.-