MCP MCP Server

Jenkins MCP server with bearer token authentication support

Local serverstdio

What is the MCP MCP server?

Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Jenkins MCP server with bearer token authentication support. The mcp mcp server is what makes that connection.

What the server does

Add the server to your MCP client config. The recommended approach uses environment variables:

  • 38 tools — — covers ~95% of the Jenkins API: jobs, builds, nodes, views, queue, plugins, and system operations
  • Bearer token auth — — supports both classic API token and modern bearer token authentication
  • Multiple instances — — connect to several Jenkins servers simultaneously using comma-separated env vars
  • Pipeline awareness — — retrieve stage-by-stage pipeline status, console logs, test results, and build artefacts
  • Node management — — list agents, toggle nodes online/offline, and inspect system info without leaving your AI client
  • Zero-install usage — — run directly via npx --yes @kud/mcp-jenkins@latest with no local setup required

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Category — Tools
  • Views — jenkins_list_views, jenkins_get_view
  • Tools — The Tools tool exposed by this server

Installation

Installation goes through your MCP client rather than a global install: point it at @kud/mcp-jenkins on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: MCP_JENKINS_URL, MCP_JENKINS_USER, MCP_JENKINS_API_TOKEN, MCP_JENKINS_BEARER_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Category, Views, Tools — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CategoryTools
Viewsjenkins_list_views, jenkins_get_view
ToolsThe Tools tool exposed by this server.

How to install the MCP MCP server

{
  "mcpServers": {
    "jenkins-1": {
      "command": "npx",
      "args": ["-y", "@kud/mcp-jenkins"],
      "env": {
        "MCP_JENKINS_URL": "your-value",
        "MCP_JENKINS_USER": "your-value",
        "MCP_JENKINS_API_TOKEN": "your-value",
        "MCP_JENKINS_BEARER_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_JENKINS_URLEndpoint or connection string the server talks to.Yes
MCP_JENKINS_USERConfiguration value read at startup.Optional
MCP_JENKINS_API_TOKENCredential the server authenticates with.Yes
MCP_JENKINS_BEARER_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to Category.
  • Use MCP to Views.
  • Use MCP to Tools.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Category, Views, Tools) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.