jenkins

This Jenkins MCP Server provides a bridge between Claude and your Jenkins instance, enabling automated Jenkins management via the MCP protocol. It exposes tools for discovering and interacting with Jenkins jobs, triggering builds (with parameters), retrieving build statuses and logs, accessing build histories, and monitoring the Jenkins queue. You can view and manage folder structures, monitor console output for debugging, and get detailed information about specific builds. The available tools are designed to be used through MCP requests from Claude, allowing you to compose concise commands to perform common CI/CD tasks without switching contexts to the Jenkins UI.

To use the server, ensure the MCP client (Claude) can reach the Jenkins MCP server endpoint and that the Jenkins connection credentials are correctly configured in the environment. Start the server (via npm start in development or your deployment method) and then invoke the provided tools such as get_build_status, trigger_build, get_build_log, list_jobs, get_build_history, stop_build, get_queue, and get_job_config. For example, you can trigger a parameterized build for a given job path, retrieve its latest status, and pull the corresponding console log for troubleshooting.

Prerequisites:

• Node.js (14.x or newer) and npm installed on your system
• Access to a Jenkins server with API token-based authentication

Installation steps:

1. Clone the repository: git clone https://github.com/ddang-jung/jenkins-mcp-server.git cd jenkins-mcp-server

2. Install dependencies: npm install

3. Build the project: npm run build

4. Run the server (development): npm start

5. Configure Claude Desktop or your MCP client to point to the built index.js and provide Jenkins credentials (JENKINS_URL, JENKINS_USER, JENKINS_TOKEN) in the environment.

Notes:

• In production, bundle the build artifacts and deploy the server using your preferred process manager (e.g., systemd, PM2) and ensure environment variables are securely managed.

Environment variables and configuration:

• JENKINS_URL: URL to the Jenkins instance
• JENKINS_USER: Jenkins username with API access
• JENKINS_TOKEN: Jenkins API token (recommended) or password

Common issues:

• Authentication failures: verify credentials and token scope
• Incorrect job paths: use the Jenkins job path format (e.g., job/MyProject)
• Network connectivity: ensure the Jenkins server is reachable from the MCP server

Debugging:

• Enable debug logging by setting DEBUG=jenkins-mcp-server in your environment
• Check Jenkins REST API documentation for endpoint specifics

For Claude Desktop configuration, you typically point to the built index.js and supply Jenkins connection details in the env block.