woodpecker-mcp
Related Servers
Alternatives to woodpecker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Woodpecker CI: read repositories, pipelines and logs, and drive builds, secrets and crons7153 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that connects AI assistants to Woodpecker CI for debugging pipeline failures, analyzing build logs, and troubleshooting CI/CD configurations.13MIT
- AlicenseNot gradedqualityCmaintenanceRead-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 npmISC
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- AlicenseAqualityAmaintenanceRead-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.415 npm1ISC
- AlicenseNot gradedqualityCmaintenanceAn 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
TDQS
Scored across 5 tools
Each tool targets a distinct resource: instances, repos, pipelines, pipeline details, and step logs. There is no overlap, and the descriptions clearly indicate the unique role of each tool.
Tool names follow a consistent list_/get_ convention, with plural nouns for collection listings (list_instances, list_repos, list_pipelines) and singular for item retrieval (get_pipeline, get_step_logs). The pattern is predictable and readable.
With five tools, the server is well-scoped for its purpose of inspecting Woodpecker CI instances, repositories, pipelines, and logs. Each tool fills a necessary role without redundancy.
The tool set forms a complete read-only workflow: from listing instances to listing repos, drilling into pipelines, getting pipeline details with step states, and fetching failed step logs. There are no dead ends or missing operations for the evident use case.