woodpecker-mcp
Related Servers
Alternatives to woodpecker-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables querying cross-repo code dependencies, HTTP routes, database tables, and queues via an MCP server using Cypher queries.-
- AlicenseNot gradedqualityBmaintenanceExposes code graphs across multi-program repositories via MCP, enabling humans and agents to query the fleet with evidence.MIT
- AlicenseAqualityDmaintenanceExposes a dependency graph of strategic sourcing artifacts and analyses as an MCP server, enabling navigation of phases, analyses, deliverables, and graph traversal for impact analysis and build order.16Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables querying a Neo4j knowledge graph built from Git repositories and relational database schemas via MCP, with tools for schema inspection, Cypher queries, and searching code and database entities.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Neo4j graph database operations, enabling Cypher queries, node/relationship management, and schema discovery.1BSD 3-Clause
- FlicenseNot gradedqualityCmaintenanceExposes a Neo4j graph database as MCP tools, enabling AI agents to run read and write Cypher queries.-
TDQS
Scored across 5 tools
Each tool serves a distinct role: detecting blind spots, diagnosing root causes, computing blast radius, providing service health, and retrieving topology. Minimal overlap, clear boundaries.
All tools follow a consistent 'woodpecker_verb_noun' pattern using snake_case, e.g., woodpecker_detect_blind_spots, woodpecker_get_topology. No deviations.
With 5 tools covering topology, health, blind spots, root cause, and blast radius, the set is well-scoped for diagnostic purposes without being excessive or thin.
The set provides a complete workflow for service dependency analysis: establish topology, check health, detect blind spots, find root cause, and compute blast radius. No obvious gaps for the intended domain.