legwork-mcp
Related Servers
Alternatives to legwork-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to extract information from GitHub repositories, including repository summaries, project directory structure, and file contents. It exposes these capabilities as tools that can be invoked directly from a natural-language chat session.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to quickly extract information about GitHub repositories, including repository summaries, project directory structures, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to quickly extract information about GitHub repositories, including repository summaries, project directory structures, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, Cursor, and Windsurf to quickly extract information about GitHub repositories, including repository summaries, project directory structure, and file content.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to extract GitHub repository information, including summaries, directory structure, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract GitHub repository summaries, project directory structures, and file contents. It supports clients such as Claude Desktop, Cline, and Cursor.-
TDQS
Scored across 5 tools
Each tool targets a distinct phase: find_tools (search), install_tool (build), install_status (check in-progress install), list_installed_tools (enumerate), use_tool (invoke). The only mild overlap is between install_status and list_installed_tools, but descriptions clearly separate in-progress builds from already-installed inventory.
All names follow a verb_noun pattern (find_tools, install_tool, install_status, list_installed_tools, use_tool) and use snake_case throughout. Minor inconsistency in singular/plural (tool vs tools), but the convention is otherwise predictable.
Five tools is well-scoped for a discover-install-run lifecycle. Each tool earns its place with no redundant entries in this range.
The full forward lifecycle (find, install, status, list, use) is covered cleanly. The notable gap is the absence of any uninstall/remove or update operation, which an agent might need to manage installed state, but core workflows are workable.