PlugWiki

Jenkins MCP servers: which one to use

Use the official Jenkins MCP Server plugin if you can install plugins. Use mcp-jenkins if you cannot, or if you want a read-only flag.

Servers
22
active
Official
1
by Jenkins
Hosted
1
nothing to install
Local
14
runs on your machine

The official Jenkins MCP Server plugin turns your Jenkins into an MCP server. Assistants such as Claude Code, Cursor and GitHub Copilot Chat connect to it over HTTP with a Jenkins API token. It can trigger, cancel and replay builds, so the token's Jenkins permissions are your safety limit. If you cannot add plugins to your controller, run a community server such as mcp-jenkins on your own machine instead. Its README documents a --read-only flag.

Good for

  • Developers who want Claude Code or Cursor to read build logs and find why a build failed
  • Jenkins admins who can install plugins and want assistants to connect to Jenkins directly
  • Teams that cannot change the Jenkins controller and need a server on their own machine
  • People who want an assistant to look at builds without starting them

Which Jenkins MCP server to use

Use the official plugin when you control the Jenkins server, because assistants then connect straight to it. Pick mcp-jenkins when you cannot install plugins or want its read-only flag.

ServerOfficialRunsSign-inRead-only optionGitHub stars
Jenkins MCP Server pluginOfficialInside JenkinsAPI token–119
mcp-jenkinsCommunityLocalPassword or tokenRead-only flag157
@kud/mcp-jenkinsCommunityLocalAPI or bearer token–19
Jenkins MCP EnterpriseCommunityLocalAPI token–30
jenkins-mcp-serverCommunityLocalAPI token–14

All Jenkins MCP servers

22 active · 1 official · official first, then by GitHub stars

Show all 22

Questions

Is there an official Jenkins MCP server?

Yes. The Jenkins MCP Server plugin lives in the jenkinsci GitHub organization. You install it on your Jenkins controller, and it adds MCP endpoints to Jenkins itself.

What is the difference between the plugin and the community servers?

The plugin runs inside Jenkins, so assistants connect straight to it over HTTP. Community servers such as mcp-jenkins and @kud/mcp-jenkins run on your own machine and call the Jenkins API with your credentials.

How does the official plugin sign in?

It uses the same credentials as Jenkins. Create an API token on your Jenkins user and send it as an HTTP Basic header. The README shows this for Claude Code, Cursor and VS Code.

Does it work with Claude, ChatGPT and Cursor?

Claude Code and Cursor have setup steps in the plugin README, and the author tested GitHub Copilot Chat in VS Code. The README has no ChatGPT setup steps.

Can it start or cancel builds?

Yes. The official plugin can trigger, cancel, rebuild and replay builds, and it can create pipeline jobs. Give the API token a Jenkins user that can only do what you are happy for an assistant to do.

Is there a read-only Jenkins MCP server?

mcp-jenkins has a --read-only flag, off by default (its README option table). The plugin README lists no such flag, so limit what the Jenkins user behind the token can do.

How many tools do the servers list?

@kud/mcp-jenkins says it has 38 tools covering jobs, builds, nodes, views, the queue and plugins. The official plugin lists tools for jobs, builds, test results, source control and system logs.

Which one handles several Jenkins servers?

Jenkins MCP Enterprise routes each call to the right Jenkins instance by URL, and @kud/mcp-jenkins can connect to several servers at once. Enterprise is GPL-3.0 licensed and can add vector search.

Are they free?

Yes. The official plugin, mcp-jenkins and @kud/mcp-jenkins are MIT licensed open source.

Server facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Archived servers are not listed.