Skip to main content
Glama
ni-c

woodpecker-ci-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to woodpecker-ci-mcp

No user-submitted related servers found.

    Related Servers

    • woodpecker-mcp

      RikiGomes
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for Woodpecker CI that allows AI agents to check pipeline status and retrieve step logs across multiple self-hosted instances.
      5
      MIT

    • 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

    • fj-mcp

      jairov4
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.
      -

    • gitlab-ci-mcp

      mshegolev
      A
      license
      A
      quality
      B
      maintenance
      MCP server for GitLab CI/CD — pipelines, jobs, schedules, branches, tags, merge requests and repository files. Works with any GitLab (SaaS gitlab.com or self-hosted) via python-gitlab.
      23
      46 PyPI
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 71 tools

    Disambiguation4/5

    Nearly every tool targets a distinct resource-action pair, and the descriptions are unusually precise at clarifying edge cases. A few near-neighbor pairs (get_queue_info vs list_queued_pipelines, get_pipeline_config vs get_pipeline_metadata) still demand careful reading, and with 71 tools the selection burden is real.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun pattern: get_, list_, create_, update_, delete_, trigger_, cancel_, approve_, pause_, resume_, etc. Resource nouns are uniform across the set, making the surface highly predictable even at this scale.

    Tool Count1/5

    71 tools falls squarely into the extreme-mismatch band and is far beyond a comfortably surveyable surface. Even though each tool maps to a real API action, the agent context cost and selection complexity are overwhelming; this set would be better split into smaller domain-specific servers.

    Completeness5/5

    The tool set provides full lifecycle coverage for secrets, registries, agents, crons, repositories, pipelines, users, forges, organizations, logs, and queue/server administration. There are no obvious dead ends, and even high-risk operations like log deletion, agent draining, and queue pausing have dedicated tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources