Skip to main content
Glama
RikiGomes

woodpecker-mcp

by RikiGomes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to woodpecker-mcp

No user-submitted related servers found.

    Related Servers

    • woodpecker-mcp

      j04n-f
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects AI assistants to Woodpecker CI for debugging pipeline failures, analyzing build logs, and troubleshooting CI/CD configurations.
      14
      MIT

    • Jenkins MCP Server

      ooooshino
      A
      license
      Not graded
      quality
      D
      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 npm
      ISC

    • mcp-multi-db

      mahAnuj
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.
      4
      38 npm
      1
      ISC

    • KubeWhisper

      abdulhusainahk
      A
      license
      Not graded
      quality
      D
      maintenance
      An AI-DevOps MCP server that gives LLMs read-only-by-default access to Kubernetes clusters, Prometheus metrics, and GitHub Actions, enabling natural language queries about infrastructure status and safe write operations with previews.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, and the descriptions explicitly separate similar-sounding tools such as get_step_logs vs. diagnose_pipeline and list_pipelines vs. recent_activity. No pair appears interchangeable, so an agent should be able to select the right tool confidently.

    Naming Consistency4/5

    All names use snake_case and almost all follow a verb_noun pattern (get_, list_, compare_, diagnose_, restart_, cancel_, trigger_, run_). recent_activity is the main outlier as a noun phrase, but it remains clear and unique.

    Tool Count4/5

    At 19 tools this is slightly above the ideal compact range, but the broad CI surface (pipelines, logs, config, crons, secrets, agents, queue) justifies most of them. Each tool appears to earn its place rather than duplicating another.

    Completeness4/5

    The core pipeline lifecycle is well covered: discovery, inspection, config, logs, failure diagnosis, comparison, triggering, restarting, and cancellation. Gaps exist around management of crons, secrets, agents, and the queue, but those are administrative operations outside the core triage workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources