Skip to main content
Glama
gcorroto
by gcorroto

Related Servers

Alternatives to MCP-Jenkins

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol (MCP) server that enables AI tools like chatbots to interact with and control Jenkins, allowing users to trigger jobs, check build statuses, and perform other Jenkins operations through natural language.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Jenkins (with optional GitLab integration) that lets AI assistants list jobs, trigger and track deployments, fetch build logs, and verify whether tickets are deployed, without touching the Jenkins UI.
      17
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Jenkins CI/CD servers, providing tools to check build statuses, trigger builds, and retrieve build logs.
      3
      15
      MIT
    • 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.
      36 npm
      14
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enterprise-grade MCP server for Jenkins CI/CD integration that enables AI assistants to diagnose build failures, analyze pipelines, and search logs through natural conversation.
      6
      GPL 3.0

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific Jenkins resources and actions, with no overlapping functionality. For example, jenkins_get_coverage_lines and jenkins_get_coverage_paths serve different coverage-related queries, while jenkins_start_job and jenkins_stop_job handle opposite lifecycle actions.

    Naming Consistency5/5

    All tools follow a perfectly consistent 'jenkins_verb_noun' naming pattern using snake_case throughout. The structure is predictable with the server prefix, action verb, and resource noun clearly separated, making it easy for agents to parse and understand.

    Tool Count5/5

    With 11 tools, this server is well-scoped for Jenkins CI/CD operations, covering job management, build monitoring, coverage reporting, and input handling. Each tool earns its place without redundancy, providing a comprehensive yet manageable interface for typical Jenkins automation tasks.

    Completeness4/5

    The toolset covers core Jenkins workflows including job control (start/stop/status), build monitoring (steps/node/actions), and code coverage reporting. Minor gaps exist, such as missing job configuration management or artifact retrieval tools, but agents can accomplish most essential CI/CD operations with this surface.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive