MCP server
by ashwinighuge3012
Jenkins CI/CD integrates seamlessly to manage jobs, monitor builds, and automate DevOps workflows with robust caching an
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.
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.
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.
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Jenkins CI/CD for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Jenkins CI/CD surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Jenkins CI/CD reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Jenkins CI/CD is the kind of server we cite when onboarding engineers to host + tool permissions.
Jenkins CI/CD is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We wired Jenkins CI/CD into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Jenkins CI/CD is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Jenkins CI/CD against two servers with overlapping tools; this profile had the clearer scope statement.
Jenkins CI/CD has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Jenkins CI/CD has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 28
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.
# Global installation
npm install -g @ashwinighuge/jenkins-mcp-server
# Or use directly with npx
npx @ashwinighuge/jenkins-mcp-server --help
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"
}
}
}
}
# Install globally for system-wide access
npm install -g @ashwinighuge/jenkins-mcp-server
# Verify installation
jenkins-mcp --help
# 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
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
# 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
| Mode | Use Case | Command |
|---|---|---|
| STDIO | Claude Desktop, direct MCP clients | jenkins-mcp |
| HTTP | MCP Gateway, web integrations | jenkins-mcp --transport streamable-http |
# 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
Here is a list of the tools exposed by this MCP server:
trigger_jobjob_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.get_job_infojob_name (string): The name of the Jenkins job.get_build_statusjob_name (string): The name of the Jenkins job.build_number (integer): The build number.get_console_logjob_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.list_jobsrecursive (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 jobssearch_jobspattern (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 jobsget_queue_infoserver_infoget_pipeline_statusjob_name (string): The name of the Jenkins Pipeline job.build_number (integer): The build number.list_build_artifactsjob_name (string): Name of the Jenkins job.build_number (integer): Build number to list artifacts for.download_build_artifactjob_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).search_build_artifactsjob_name (string): Name of the Jenkins job to search.pattern (string): Pattern to match artifact names (wildcardsPrerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.