Jenkins MCP

by kjozsa

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Related Servers

Alternatives to Jenkins MCP

No user-submitted related servers found.

Related Servers

Jenkins MCP Server
CI/CD & DevOps Developer Tools
avisangle
A
license
Not graded
quality
D
maintenance
Enables Jenkins CI/CD integration with job management, pipeline monitoring, artifact handling, and batch operations via MCP.
Updated 7 months ago (2026-02-13 02:16 UTC)
17 npm
4
Apache 2.0
Jenkins MCP Proxy
CI/CD & DevOps Developer Tools
ravi11196
F
license
Not graded
quality
D
maintenance
Enables AI agents and external systems to programmatically trigger and monitor Jenkins jobs, retrieve build status and logs via MCP standards.
Updated 3 months ago (2026-06-19 14:38 UTC)
-
Jenkins MCP Server
CI/CD & DevOps Developer Tools
AshwiniGhuge3012
A
license
Not graded
quality
D
maintenance
An MCP server for interacting with a Jenkins CI/CD server. Allows you to trigger jobs, check build statuses, and manage your Jenkins instance through MCP.
Updated a year ago (2025-08-10 09:28 UTC)
17 npm
14
Apache 2.0
jenkins-mcp-server
CI/CD & DevOps Developer Tools
LokiMCPUniverse
F
license
A
quality
D
maintenance
Exposes a Jenkins controller's REST API to MCP-compatible clients, enabling job management, build triggering, and log retrieval through natural language.
Updated 5 months ago (2026-04-18 15:23 UTC)
11
4
-
Jenkins MCP Server
CI/CD & DevOps Developer Tools
manjunath031984
F
license
Not graded
quality
B
maintenance
Exposes Jenkins CI/CD capabilities as MCP tools, including job management, builds, pipelines, and Terraform/GCP log inspection.
Updated 2 months ago (2026-07-17 13:15 UTC)
-
jenkins-mcp
CI/CD & DevOps Developer Tools
stubbedev
A
license
Not graded
quality
A
maintenance
MCP server for Jenkins to inspect builds, control jobs, and manage pipeline configuration.
Updated 6 days ago (2026-09-15 04:41 UTC)
16 npm
MIT

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored 2026-04-18 11:35 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_build_status retrieves status information, list_jobs enumerates available jobs, and trigger_build initiates new builds. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (get_build_status, list_jobs, trigger_build). The verbs are descriptive and appropriate for their actions, and snake_case is used uniformly throughout.

Tool Count2/5

With only 3 tools, the set feels thin for a Jenkins integration, which typically involves more operations like viewing logs, managing job configurations, or canceling builds. This limited scope may hinder agent workflows that require broader control.

Completeness2/5

The toolset is severely incomplete for Jenkins automation. It lacks essential operations such as viewing build logs, updating job configurations, canceling builds, or managing nodes/plugins. This creates significant gaps that will likely cause agent failures in common use cases.