Skip to main content
Glama
Jenkins MCP Server

Jenkins MCP Server

by TelmanH

Related Servers

Alternatives to Jenkins MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to query application projects directly for logs, metrics, incidents, and semantic search through read-only tools.
      17
      63 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to analyze, cluster, compare, and export reports from local log files through seven read-only tools, returning compact evidence packs with line-number citations instead of raw log dumps. All processing happens on the local machine, so log data never leaves the environment.
      80 PyPI
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.
      16
      61 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to access evidence-backed repository memory, code graph, project DNA, and deterministic change validation so they understand design decisions, past bugs, and invariants while working.
      1,900 npm
      18
      Functional Source , Version 1.1, ALv2 Future
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP service for production troubleshooting that lets you register database, log, code, and message-queue connections in a web console, then have AI clients query them safely by target name. Models never supply hosts, accounts, or passwords themselves, and all operations are restricted to a read-only whitelist with audit logging.
      603 PyPI
      3
      MIT

    TDQS

    A3.7/5.0

    Scored across 34 tools

    Disambiguation4/5

    Purpose clusters (log inspection, artifacts, jobs, nodes, knowledge base) are well delineated and descriptions give explicit guidance like 'START HERE' and 'use this instead'. The main risk is the dense family of log tools (get_build_summary, get_log_errors, get_stage_log, search_log, get_log_lines, recurring_errors) where boundaries are clear only after reading the full descriptions.

    Naming Consistency4/5

    Mostly verb_noun snake_case (get_build_summary, list_jobs, compare_builds, read_artifact, find_known_issues). A handful drop the verb (node_health, failures_overview, recent_builds, recurring_errors), which is a minor but noticeable deviation from the otherwise predictable pattern.

    Tool Count3/5

    34 tools is heavy, well above the comfortable 3-15 range. The Jenkins debugging domain is genuinely broad (logs, artifacts, jobs, config, nodes, queue, KB, workspace) and most tools earn their place, but the surface is large enough to burden tool selection.

    Completeness5/5

    Coverage is unusually thorough across builds, logs, artifacts, test failures, job/node/queue state, config history and diffing, knowledge base lifecycle, and workspace reads. The only apparent gap is write/action operations (triggering, aborting, approving inputs), which seem intentionally excluded as a safety choice and are explained as such.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues