Skip to main content
Glama

Related Servers

Alternatives to jankins

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      A
      quality
      C
      maintenance
      MCP server that connects AI agents to Jenkins, supporting stdio and HTTP transports with tools for jobs, builds, logs, and queue management.
      9
      75
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Jenkins CI, enabling AI agents to securely query job/build status, logs, artifacts, and generate verification reports for loop workflows.
      17
      ISC
    • 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

    TDQS

    A3.5/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have distinct purposes (job management, build inspection, test analysis, pipeline, queue, user info). Some overlap exists between log-related tools (analyze_build_log vs search_log vs tail_log_live) but descriptions clarify their unique functions. SCM tools (get_build_scm vs get_build_changes) are also clearly separated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_build_log, compare_runs, disable_job). No mixed conventions or inconsistent naming styles are observed.

    Tool Count4/5

    25 tools is slightly above the ideal range (3-15) but is reasonable for a comprehensive Jenkins integration covering jobs, builds, tests, pipelines, queue, and user info. The count is earned given the breadth of functionality.

    Completeness4/5

    The tool set covers major CI/CD workflows: job management (list, get, enable/disable, trigger), build inspection (logs, artifacts, SCM, comparisons), test analysis, pipeline visualization, queue, and user info. Missing: job creation/deletion, build cancellation, and configuration editing, but core troubleshooting and monitoring are well-represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues