A
licenseNot graded
qualityA
maintenanceExposes ReadyAgents' local workflow engine and built-in tools over MCP stdio, enabling MCP clients to define, run, inspect, and approve YAML/JSON agent workflows.
101 PyPI
Apache 2.0
sdlc-workflow-mcp
by Tingsum26
Related Servers
Alternatives to sdlc-workflow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables locally configured MCP servers to be called over stdio and mixed with xAI server-side tools, without relying on hosted xAI MCP.MIT
- AlicenseCqualityDmaintenanceConnects MCP-enabled editors to GitHub Copilot CLI for non-interactive code analysis, batch processing, and code review.1027 npm5MIT
- AlicenseAqualityDmaintenanceWraps GitHub Copilot CLI as an MCP server, enabling MCP clients to run Copilot conversations for code tasks with support for session resumption and permission modes.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables ContextForge to interact with Unreal Engine's official local MCP server via a stable stdio-to-HTTP adapter, supporting toolset listing, description, and invocation.MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server that bridges Beale research workspaces to Claude Code, providing typed memory, workspace search, revisioned runbooks, and research profile context via a stdio plugin.MIT
TDQS
C2.7/5.0
Scored across 42 tools
Disambiguation3/5
While most tools have distinct verbs and resources, there is overlap among the many graph/onboarding/analysis tools (e.g., workflow_get_repository_graph, workflow_get_journey_graph, workflow_analyze_journey, workflow_analyze_http_dependencies) and between workflow_ticket_advance and advance_repo_task. Descriptions help clarify, but the sheer number of similar read/analysis operations could still lead to misselection.
Naming Consistency3/5
All names use snake_case, but the ordering is inconsistent: some follow workflow_<entity>_<action> (workflow_epic_create) while others follow workflow_<action>_<object> (workflow_get_task_context). One tool (advance_repo_task) also lacks the workflow_ prefix, making the convention mixed though still readable.
Tool Count2/5
42 tools far exceeds the 3-15 sweet spot and the rubric's 25+ threshold for 'too many,' making the surface heavy even for a complex SDLC domain. While each tool may have a distinct purpose, the volume increases cognitive load and selection risk.
Completeness4/5
The set covers a broad SDLC workflow lifecycle: epic/ticket/task creation, advancement, approvals, artifacts, decisions, blockers, onboarding, graphs, diagnostics, and identity. Some gaps exist (e.g., no explicit list/get for epics or tickets beyond task context), but core workflows are well-supported.
Maintenance
ActivitySlowing
ResponsivenessNo issues