agentic-sdlc-mcp
Related Servers
Alternatives to agentic-sdlc-mcp
No user-submitted related servers found.
Related Servers
- -licenseBqualityNot gradedmaintenanceEnables AI-driven orchestration of GitHub development workflows including automated issue analysis, code generation, code review, and PR creation through multiple specialized agents. Integrates with GitHub Actions to automate the complete development process from issue to pull request.7-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to register, self-assign and coordinate tasks, track progress, review work, and manage GitHub Projects v2 with AI-powered PRD generation, sprint planning, issue triage, and PRD-to-issues pipelines backed entirely by GitHub-native storage.301 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage GitHub repositories and automate workflows through natural language.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to self-assign and coordinate tasks, track progress and token budgets, and automate GitHub project workflows such as PRD-to-issues pipelines, sprint planning, triage, reviews, and releases.301 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.6 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage GitHub repositories, branches, issues, pull requests, releases, and actions through natural language.281 npm5MIT
TDQS
Scored across 13 tools
Tools largely map to distinct SDLC phases (context, plan, create issues, prepare work item, review, security, handoff). Minor overlap exists between release_readiness_check and quality_gate_status, and among evidence-producing tools (repo_context, sdlc_evidence_packet, agent_handoff_packet), but descriptions clarify scope.
All names use snake_case and are descriptive, with no casing inconsistencies. However, some are verb-led (create_issue_set, review_pr_against_standard) while others are noun-led (repo_context, quality_gate_status), so the pattern is not uniformly verb_noun.
13 tools is within the well-scoped range and each appears to serve a distinct SDLC stage. No obvious redundancy that bloats the set.
The surface covers context gathering, planning, issue creation, work prep, PR review, release readiness, security, and evidence. However, it lacks issue update/close, PR creation/merge, and comment operations, leaving notable lifecycle gaps for end-to-end SDLC.