Jenkins MCP Server
Related Servers
Alternatives to Jenkins MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to query application projects directly for logs, metrics, incidents, and semantic search through read-only tools.1763 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 PyPI1MIT
- AlicenseBqualityCmaintenanceProvides 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.1661 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npm18Functional Source , Version 1.1, ALv2 Future
- AlicenseNot gradedqualityBmaintenanceA 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 PyPI3MIT
- AlicenseAqualityBmaintenanceProvides AI assistants with read-only access to live construction project data and document libraries, enabling issue investigation, schedule risk scoring, and evidence-backed project briefs.6MIT
TDQS
Scored across 34 tools
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.
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.
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.
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.