Jenkins CI/CD▌

by ashwinighuge3012
Jenkins CI/CD integrates seamlessly to manage jobs, monitor builds, and automate DevOps workflows with robust caching an
Integrates with Jenkins CI/CD infrastructure to provide complete job management, build monitoring, pipeline execution, and artifact handling with intelligent caching and CSRF protection for DevOps automation workflows.
best for
- / DevOps engineers managing CI/CD pipelines
- / Automating build monitoring and deployment workflows
- / Teams needing AI-assisted Jenkins operations
capabilities
- / Trigger and monitor Jenkins jobs
- / Stream build console logs in real-time
- / Download and search build artifacts
- / Execute pipeline stages with detailed monitoring
- / Manage build queues and job scheduling
- / Filter jobs by status, results and dates
what it does
Connects AI assistants to Jenkins CI/CD servers for managing builds, monitoring pipelines, and handling artifacts. Provides comprehensive job control and real-time status tracking through a secure API.
about
Jenkins CI/CD is a community-built MCP server published by ashwinighuge3012 that provides AI assistants with tools and capabilities via the Model Context Protocol. Jenkins CI/CD integrates seamlessly to manage jobs, monitor builds, and automate DevOps workflows with robust caching an It is categorized under developer tools.
how to install
You can install Jenkins CI/CD in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Jenkins CI/CD is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Jenkins MCP Server
An enterprise-grade MCP (Model Context Protocol) server for seamless Jenkins CI/CD integration. Enables AI assistants like Claude to interact with Jenkins through a comprehensive, production-ready API.
🚀 Quick Start
npm Installation (Recommended)
# Global installation
npm install -g @ashwinighuge/jenkins-mcp-server
# Or use directly with npx
npx @ashwinighuge/jenkins-mcp-server --help
Claude Desktop Integration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"jenkins": {
"command": "jenkins-mcp",
"env": {
"JENKINS_URL": "http://your-jenkins-server:8080",
"JENKINS_USER": "your-username",
"JENKINS_API_TOKEN": "your-api-token"
}
}
}
}
✨ Features
- 🔧 Job Management: Trigger, list, search, and monitor Jenkins jobs with full folder support
- 📊 Build Status: Real-time build status tracking and console log streaming
- 🔄 Pipeline Support: Stage-by-stage pipeline execution monitoring with detailed logs
- 📦 Artifact Management: List, download, and search build artifacts across multiple builds
- ⚡ Batch Operations: Parallel job execution with intelligent priority queuing
- 🚀 Performance Caching: Multi-tier intelligent caching system with automatic invalidation
- 🔍 Advanced Filtering: Filter jobs by status, results, dates, and more with regex support
- 📋 Queue Management: Real-time build queue monitoring and management
- 🔒 Enterprise Security: CSRF protection, 2FA support, and secure authentication
- 🌐 Cross-Platform: Works on Windows, macOS, and Linux
- 🔄 Retry Logic: Built-in exponential backoff for improved reliability
- 📡 Transport Flexibility: Supports both STDIO and HTTP transports
- ✅ Input Validation: Robust Pydantic-based validation and error handling
📋 Prerequisites
- Node.js: 14.0.0 or higher
- Python: 3.12 or higher
- Jenkins: 2.401+ (recommended)
- Jenkins API Token: For authentication
🛠 Installation Methods
Method 1: npm (Recommended)
# Install globally for system-wide access
npm install -g @ashwinighuge/jenkins-mcp-server
# Verify installation
jenkins-mcp --help
Method 2: Development Setup
# Clone the repository
git clone https://github.com/AshwiniGhuge3012/jenkins-mcp-server
cd jenkins-mcp-server
# Install Node.js dependencies
npm install
# Install Python dependencies
pip install -r requirements.txt # or use uv pip install
# Run locally
node bin/jenkins-mcp.js --help
🔐 Configuration
Environment Variables
Create a .env file in your working directory:
# Required Jenkins Configuration
JENKINS_URL="http://your-jenkins-server:8080"
JENKINS_USER="your-username"
JENKINS_API_TOKEN="your-api-token"
# Optional: Server Configuration
MCP_PORT=8010
MCP_HOST=0.0.0.0
# Optional: Retry Configuration
JENKINS_MAX_RETRIES=3
JENKINS_RETRY_BASE_DELAY=1.0
JENKINS_RETRY_MAX_DELAY=60.0
JENKINS_RETRY_BACKOFF_MULTIPLIER=2.0
# Optional: Performance Cache Configuration
JENKINS_CACHE_STATIC_TTL=3600 # 1 hour
JENKINS_CACHE_SEMI_STATIC_TTL=300 # 5 minutes
JENKINS_CACHE_DYNAMIC_TTL=30 # 30 seconds
JENKINS_CACHE_SHORT_TTL=10 # 10 seconds
JENKINS_CACHE_STATIC_SIZE=1000 # Max cached items
JENKINS_CACHE_SEMI_STATIC_SIZE=500
JENKINS_CACHE_DYNAMIC_SIZE=200
JENKINS_CACHE_PERMANENT_SIZE=2000
JENKINS_CACHE_SHORT_SIZE=100
Getting Jenkins API Token
- Log into your Jenkins instance
- Click your username → Configure
- Scroll to API Token section
- Click Add new Token
- Give it a name and click Generate
- Copy the generated token (save it securely!)
🚀 Usage
Command Line Interface
# STDIO mode (default, for Claude Desktop)
jenkins-mcp
# HTTP mode (for MCP Gateway)
jenkins-mcp --transport streamable-http --port 8010
# Custom host and port
jenkins-mcp --transport streamable-http --host localhost --port 9000
# Show help
jenkins-mcp --help
Transport Modes
| Mode | Use Case | Command |
|---|---|---|
| STDIO | Claude Desktop, direct MCP clients | jenkins-mcp |
| HTTP | MCP Gateway, web integrations | jenkins-mcp --transport streamable-http |
Advanced Usage Examples
# Using with npx (no global installation)
npx @ashwinighuge/jenkins-mcp-server
# Using environment variables
JENKINS_URL=http://localhost:8080 JENKINS_USER=admin JENKINS_API_TOKEN=abc123 jenkins-mcp
# HTTP mode with custom configuration
jenkins-mcp --transport streamable-http --host 0.0.0.0 --port 8080
Available Tools
Here is a list of the tools exposed by this MCP server:
trigger_job
- Description: Triggers a Jenkins job with optional parameters.
- Parameters:
job_name(string): The name of the Jenkins job.params(object, optional): Job parameters as a JSON object. For multiselect parameters, pass an array of strings.
- Returns: A confirmation message with the queue URL.
get_job_info
- Description: Gets detailed information about a Jenkins job, including its parameters.
- Parameters:
job_name(string): The name of the Jenkins job.
- Returns: An object containing the job's description, parameters, and last build number.
get_build_status
- Description: Gets the status of a specific build.
- Parameters:
job_name(string): The name of the Jenkins job.build_number(integer): The build number.
- Returns: An object with the build status, timestamp, duration, and URL.
get_console_log
- Description: Retrieves the console log for a specific build.
- Parameters:
job_name(string): The name of the Jenkins job.build_number(integer): The build number.start(integer, optional): The starting byte position for fetching the log.
- Returns: The console log text and information about whether more data is available.
list_jobs
- Description: Lists all available jobs on the Jenkins server with advanced filtering capabilities.
- Parameters:
recursive(boolean, optional): If True, recursively traverse folders (default: True)max_depth(integer, optional): Maximum depth to recurse (default: 10)include_folders(boolean, optional): Whether to include folder items (default: False)status_filter(string, optional): Filter by job status: "building", "queued", "idle", "disabled"last_build_result(string, optional): Filter by last build result: "SUCCESS", "FAILURE", "UNSTABLE", "ABORTED", "NOT_BUILT"days_since_last_build(integer, optional): Only jobs built within the last N daysenabled_only(boolean, optional): If True, only enabled jobs; if False, only disabled jobs
- Returns: A list of jobs with enhanced metadata including build status and timestamps.
search_jobs
- Description: Search for Jenkins jobs using pattern matching with advanced filtering.
- Parameters:
pattern(string): Pattern to match job names (supports wildcards like 'build*', 'test', etc.)job_type(string, optional): Filter by type - "job", "folder", or "all" (default: "job")max_depth(integer, optional): Maximum depth to search (default: 10)use_regex(boolean, optional): If True, treat pattern as regex instead of wildcard (default: False)status_filter(string, optional): Filter by job status: "building", "queued", "idle", "disabled"last_build_result(string, optional): Filter by last build result: "SUCCESS", "FAILURE", "UNSTABLE", "ABORTED", "NOT_BUILT"days_since_last_build(integer, optional): Only jobs built within the last N daysenabled_only(boolean, optional): If True, only enabled jobs; if False, only disabled jobs
- Returns: A list of matching jobs with enhanced metadata and full paths.
get_queue_info
- Description: Gets information about builds currently in the queue.
- Parameters: None
- Returns: A list of items in the queue.
server_info
- Description: Gets basic information about the Jenkins server.
- Parameters: None
- Returns: The Jenkins version and URL.
get_pipeline_status
- Description: Gets detailed pipeline stage status for Jenkins Pipeline job builds.
- Parameters:
job_name(string): The name of the Jenkins Pipeline job.build_number(integer): The build number.
- Returns: Pipeline execution details including stage-by-stage status, timing, duration, and logs.
list_build_artifacts
- Description: List all artifacts for a specific Jenkins build.
- Parameters:
job_name(string): Name of the Jenkins job.build_number(integer): Build number to list artifacts for.
- Returns: Information about all artifacts including filenames, sizes, and download URLs.
download_build_artifact
- Description: Download a specific build artifact content (text-based artifacts only for safety).
- Parameters:
job_name(string): Name of the Jenkins job.build_number(integer): Build number containing the artifact.artifact_path(string): Relative path to the artifact (from list_build_artifacts).max_size_mb(integer, optional): Maximum file size to download in MB (default: 50MB).
- Returns: Artifact content (for text files) or download information.
search_build_artifacts
- Description: Search for artifacts across recent builds of a job using pattern matching.
- Parameters:
job_name(string): Name of the Jenkins job to search.pattern(string): Pattern to match artifact names (wildcards
FAQ
- What is the Jenkins CI/CD MCP server?
- Jenkins CI/CD is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Jenkins CI/CD?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Jenkins CI/CD is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Jenkins CI/CD against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Jenkins CI/CD is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Jenkins CI/CD reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Jenkins CI/CD for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Jenkins CI/CD surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Jenkins CI/CD has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Jenkins CI/CD benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Jenkins CI/CD into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Jenkins CI/CD is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.