Skip to main content
Glama
Sign In
woodpecker-ci-mcp

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
      A
      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.
      19
      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.
      -

    • ntfy-mcp

      ni-c
      A
      license
      A
      quality
      A
      maintenance
      MCP server for ntfy: publish notifications, read cached messages, manage users and topic access
      13
      85 npm
      1
      MIT

    • gitlab-ci-mcp

      mshegolev
      A
      license
      A
      quality
      A
      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.
      24
      316 PyPI
      2
      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

    A3.8/5.0

    Scored across 71 tools

    Disambiguation4/5

    Tools are mostly distinct with detailed descriptions that differentiate similar operations. However, some related tools like get_queue_info vs list_queued_pipelines, and the repository lifecycle tools (activate/repair/move/chown/update) could be confused without careful reading, though descriptions mitigate.

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout, with lookup_ used consistently for id resolution. No mixing of conventions.

    Tool Count2/5

    71 tools far exceeds the recommended 3-15 range; while each covers a distinct operation, the sheer number increases selection burden and cognitive load for an agent. The scope is large but the count is excessive.

    Completeness4/5

    Comprehensive CRUD coverage for most entities, but lifecycle gap: activate_repository exists without a corresponding deactivate_repository to disable a repo without deleting it. Other minor gaps possible but core workflows covered.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources