MCP Catalogs
Home

mcp-jenkins

by lanbaoshen·120·Score 47

MCP server for Jenkins integration, providing tools to interact with Jenkins CI/CD through AI assistants.

developer-toolsops-infraproductivity
46
Forks
5
Open issues
this month
Last commit
2d ago
Indexed

Overview

The MCP Jenkins server bridges Jenkins CI/CD infrastructure with AI assistants through the Model Context Protocol. It enables secure, contextual interactions with Jenkins tools while maintaining data privacy. The server implements proper authentication via username/password or API tokens and supports multiple transport methods including stdio, SSE, and streamable HTTP. With comprehensive tool coverage for builds, nodes, queue items, and artifacts, it allows AI assistants to perform Jenkins operations seamlessly.

Try asking AI

After installing, here are 7 things you can ask your AI assistant:

you:AI assistant triggering Jenkins builds with custom parameters
you:Automating Jenkins infrastructure management through natural language
you:Retrieving build logs, artifacts, and test reports for analysis
you:Monitoring Jenkins builds and queue status via AI interface
you:How do I authenticate with Jenkins?
you:What transport methods are supported?
you:Can I run this in read-only mode?

When to choose this

Choose this server when your team uses Jenkins for CI/CD and wants AI assistants to manage or query pipeline status, build jobs, and Jenkins resources through natural language.

When NOT to choose this

Don't choose this if you use a different CI/CD system (like GitLab CI, GitHub Actions, or Azure DevOps) as this server is specifically designed for Jenkins integration only.

Tools this server exposes

12 tools extracted from the README
  • get_item

    Get a specific item by name.

  • get_item_config

    Get the configuration of a specific item.

  • get_all_items

    Get all items in Jenkins.

  • build_item

    Build a item.

  • get_build

    Get a specific build by job name and build number.

  • get_build_console_output

    Get the console output of a specific build.

  • stop_build

    Stop a specific build by job name and build number.

  • get_all_nodes

    Get all nodes in Jenkins.

  • get_queue_item

    Get a specific queue item by ID.

  • cancel_queue_item

    Cancel a specific queue item by ID.

  • get_view

    Get a specific view by name.

  • get_all_views

    Get the configuration of a specific view.

Comparable tools

github-actions-mcpgitlab-mcpdocker-mcpkubernetes-mcp

Installation

Installation

Using pip:

pip install mcp-jenkins
mcp-jenkins

Using uv (recommended):

pip install uv
uvx mcp-jenkins

Docker:

docker pull ghcr.io/lanbaoshen/mcp-jenkins:latest
docker run -p 9887:9887 --rm ghcr.io/lanbaoshen/mcp-jenkins:latest --transport streamable-http

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "jenkins": {
      "command": "uvx",
      "args": ["mcp-jenkins", "--jenkins-url=YOUR_JENKINS_URL", "--jenkins-username=YOUR_USERNAME", "--jenkins-password=YOUR_TOKEN"]
    }
  }
}

FAQ

How do I authenticate with Jenkins?
You can authenticate using either a username and password or a Jenkins API token. These can be provided via command line arguments (--jenkins-username, --jenkins-password) or through headers if using the HTTP transport.
What transport methods are supported?
The server supports three transport methods: stdio (default), SSE (Server-Sent Events), and streamable HTTP. You can specify your preferred transport using the --transport argument.
Can I run this in read-only mode?
Yes, you can enable read-only mode by using the --read-only flag, which will prevent any modifications to Jenkins resources.

Compare mcp-jenkins with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.