woodpecker-mcp
Related Servers
Alternatives to woodpecker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Woodpecker CI to debug pipeline failures, analyze build logs, troubleshoot configurations, and perform pipeline and repository actions such as triggering, restarting, canceling, approving, activating, and updating settings.MIT
- FlicenseNot gradedqualityBmaintenanceEnables to interact with Drone CI/CD for managing repositories, builds, cron jobs, secrets, and users.1-
- AlicenseAqualityCmaintenanceEnables AI assistants to manage and operate Venelx CI/CD pipelines through the Venelx REST API, including listing projects, triggering builds, checking status, tailing logs, accessing artifacts and workers, and diagnosing signing or GitHub access.919 npmMIT
- FlicenseCqualityBmaintenanceEnables management of Zadig CI/CD workflows, builds, services, environments, and webhooks through the Zadig OpenAPI.49-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.70 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with self-hosted Miniflux instances through the HTTP API, covering feeds, categories, entries, enclosures, icons, OPML, users, and API keys. Write operations are confirm-gated with dry-run previews and secret redaction.8 npmMIT
TDQS
Scored across 6 tools
Each tool is scoped to a distinct Woodpecker resource (system, repos, pipelines, logs, cron, secrets), making most selections clear. Minor overlap exists around log/pipeline deletion and queue-related system actions versus pipeline listing, but descriptions provide enough guidance.
All tool names follow a consistent woodpecker_<resource> snake_case convention. Actions within each tool use a predictable verb-style pattern such as list, get, create, update, delete.
Six resource-grouped tools fit the scope well; each groups a coherent set of related operations rather than proliferating one tool per action. The count is appropriate for a CI server MCP surface.
Core CI lifecycle coverage is strong: repositories, pipelines, logs, cron, secrets, and system health are all represented. Some peripheral Woodpecker areas such as agents, registries, webhooks, or broader user/org administration appear absent but are not central to most workflows.