Skip to main content
Glama
Sign In
Seetharam1999

jenkins-slack-mcp

by Seetharam1999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to jenkins-slack-mcp

No user-submitted related servers found.

    Related Servers

    • jenkins-mcp-server

      alexsarrell
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides Jenkins integration with Claude Code, enabling job management, build operations, pipeline stages, and log search via 22 tools.
      41 npm
      1
      MIT

    • MCP Jenkins

      ana8729
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables secure, contextual AI interactions with Jenkins tools, allowing users to query items, manage builds, inspect nodes, views, and plugins, run Groovy scripts, and more through natural language while maintaining data privacy and security.
      -

    • MCP Jenkins

      microtechos
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect and operate a Jenkins instance — discovering jobs, views, nodes, and plugins; reviewing build chains, parameters, last-build status, console output, test reports, and artifacts; and triggering builds, stopping runs, or answering pipeline inputs. It connects over stdio, SSE, or streamable HTTP with optional credentials, read-only mode, and a credential-free health endpoint.
      1
      MIT

    • MCP Jenkins

      cniuftvcyj
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Jenkins through secure, contextual tools for querying and managing jobs, builds, nodes, queues, views, plugins, artifacts, and Groovy scripts, with configurable authentication and read-only safety.
      -
    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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (trigger, list, stop, status, console, history). The only minor overlap is between 'status' and 'whoami', which both reveal login state but differ in detail (login check vs. user information).

    Naming Consistency5/5

    Tool names follow a consistent snake_case verb_noun pattern (e.g., trigger_build, list_jobs, stop_build). Even the bare verbs (status, whoami, logout) are standard, predictable names for their actions.

    Tool Count5/5

    13 tools is well within the ideal range for a Jenkins+Slack integration. Each tool covers a distinct aspect of the workflow—authentication, job discovery, build control, and monitoring—without unnecessary bloat.

    Completeness5/5

    The tool surface covers the full lifecycle for this domain: login/logout, job listing/details, triggering and stopping builds, status checks, console output, and history. The Slack integration is minimal but purposeful (DM on trigger), and no critical operations are missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources