mcp-ashigaru
Related Servers
Alternatives to mcp-ashigaru
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceAn MCP server that enables AI clients to autonomously discover, analyze, fix, test, submit, and track open-source contributions on GitHub through specialized tools.12-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that lets Claude Code manage GitHub issues, branches, and pull requests through natural language, automating the full development workflow from planning to closing.523 npm2MIT
- FlicenseAqualityDmaintenanceAn MCP server that automates the full software development lifecycle through an AI-driven TDD state machine. It handles everything from task decomposition and test-driven development to integration testing and automated pull request creation.4-
- AlicenseNot gradedqualityBmaintenanceMCP server for managing an autonomous dev loop from chat—onboarding, connecting GitHub, and converting plain-English requests into tested, merged pull requests.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that provides AI assistants with comprehensive GitHub developer tooling including PR analysis, code review, changelog generation, dependency auditing, commit summarization, and refactoring suggestions.5 npmISC
TDQS
Scored across 3 tools
Each tool serves a unique purpose: starting a run, monitoring status, and promoting to production. There is no overlap in functionality.
All names are simple and readable, but there is a slight inconsistency: 'promote' and 'status' are single words while 'work_ticket' is a compound. However, the style is uniform overall.
With only 3 tools, the server feels minimal for a deployment pipeline. While it covers the essential steps, additional tools like cancellation or listing runs would be expected for broader utility.
The tool set covers the core workflow (start, check, promote), but lacks common operations such as canceling a run, retrying, or viewing history. The surface is functional but not comprehensive.