MCP.so
Sign In

Jenkins MCP Server

@WinJayX

Basic information

Category

Other

Transports

stdio

Author

WinJayX

Submitted by

Win Jay

About Jenkins MCP Server

Jenkins MCP Server

Jenkins MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-jenkins-server": {
      "command": "/Users/username/.local/bin/uv -> //uv full path",
      "args": [
        "--directory",
        "/Users/username/Desktop/mcp-jenkins-server -> //project path ",
        "run",
        "server.py"
      ],
      "env": {
        "JENKINS_URL": "http://localhost:8080",
        "JENKINS_USERNAME": "xx",
        "JENKINS_PASSWORD": "xx"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Jenkins MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Jenkins Mcp?

Jenkins Mcp is a Model Context Protocol (MCP) server that provides Jenkins integration tools. It allows AI assistants to interact with a Jenkins server – retrieving job information, build details, console output, views, and triggering builds – using Jenkins API authentication.

How to use Jenkins Mcp?

Install dependencies with pip install -r requirements.txt, then configure credentials in a .env file (JENKINS_URL, JENKINS_USER, JENKINS_TOKEN) or via environment variables in the MCP client configuration. Add the server to your MCP client (e.g., Claude Desktop) by editing claude_desktop_config.json with the command and environment variables. Once connected, any MCP‑compatible assistant can call the exposed tools by name.

Key features of Jenkins Mcp

  • Retrieve Jenkins server information
  • List and inspect Jenkins jobs
  • Get recent builds and build summaries
  • View build details and console output
  • List and manage Jenkins views
  • Trigger job builds with optional parameters

Use cases of Jenkins Mcp

  • An AI assistant queries the status of recent builds for a CI/CD pipeline.
  • A developer triggers a parameterized Jenkins job directly from a chat interface.
  • Automating inspection of Jenkins server configuration and job health.
  • Debugging failed builds by fetching console output without opening the Jenkins UI.
  • Managing Jenkins views and jobs through natural language commands.

Frequently asked questions

1

What are the runtime requirements?

Python 3.10 or higher and access to a Jenkins server with API access enabled.

2

How does authentication work?

The server uses a Jenkins API token for authentication. Credentials are set via a `.env` file (`JENKINS_USER`, `JENKINS_TOKEN`) or environment variables in the MCP client configuration.

3

How do I install and add the server?

Clone the repository, run `pip install -r requirements.txt`, then add the server to your MCP client by providing the uv command, project directory, and environment variables in the client’s config JSON.

4

Does it support triggering builds with parameters?

Yes. The `trigger_job_build` tool accepts an optional `parameters` dictionary to pass to the Jenkins job.

5

Where is the server’s data stored?

No data is stored locally beyond the configuration files (`.env`). All operations are performed live against the configured Jenkins server.

Comments

More Other MCP servers