Skip to main content
Glama
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.
      28 npm
      1
      MIT

    • Jenkins MCP Server

      Anil-appari007
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jenkins CI/CD systems through natural language, providing build management, job monitoring, log analysis, and debugging capabilities.
      MIT

    • Jenkins MCP Proxy

      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.
      -
    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