A
licenseNot graded
qualityA
maintenanceEnables AI assistants to research, plan, generate requirements, map codebases, create starter projects, manage tasks, and run multi-step software development workflows through MCP tools.
18 npm
MIT
Agent Blueprint 2.0
Related Servers
Alternatives to Agent Blueprint 2.0
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research, plan, generate requirements, create starter projects, analyze codebases, and execute multi-step software development workflows through MCP tools.18 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research, plan, generate requirements, user stories, task lists, and full-stack starter projects, analyze codebases, curate context, and run multi-step software development workflows through MCP tools.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to analyze repository architecture, changed-file and diff impact, dependency and endpoint exposure, API contract compatibility, architecture boundaries, bounded capacity simulations, and security/quality evidence through MCP tools.3Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research, plan, generate requirements and user stories, scaffold starter projects, map codebases, manage tasks, curate context, and run multi-step software-development workflows through MCP-compatible clients.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to route coding tasks across local and cloud models with explicit budgets, repository planning and execution, and independent validation/repair checks.Apache 2.0
TDQS
A4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool maps to a distinct action in the task lifecycle: health (system/config check) vs status (specific task progress), plan (forward workflow) vs audit (reverse workflow), plus resume/result/cancel. The forward-vs-reverse distinction between plan and audit is explicitly described, and health vs status operate on different subjects (engine config vs task state).
Naming Consistency5/5
All seven tools use the identical blueprint_<verb> snake_case pattern (health, status, plan, audit, resume, result, cancel). No mixing of conventions or casing styles.
Tool Count5/5
Seven tools is well-scoped for an async task orchestration server, covering the essential lifecycle verbs without redundancy or padding. Each tool earns its place.
Completeness4/5
Coverage is strong: launch (plan/audit), monitor (status), retrieve (result), recover (resume), abort (cancel), and health check. The only minor gap is the absence of a tool to enumerate/list all past tasks, which status/result help work around.