Agent Blueprint
OfficialRelated Servers
Alternatives to Agent Blueprint
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAutonomous spec-to-product coding-agent CLI. Its MCP server exposes 34 tools over stdio: project state and task-queue ops, memory retrieve/store, code search, quality and verification reports, repo hotspots/co-changes, and structured findings/learnings.1,179 npm1,068Business Source 1.1
- AlicenseAqualityFmaintenanceAgent-first skill marketplace MCP server. AI agents discover, install, and share skills across 7 platforms via MCP protocol. 15 tools including skill search, download, upload, and agent discovery.184MIT
- AlicenseDqualityCmaintenanceThe intelligent execution layer for coding agents, exposed as an MCP server for high-stakes engineering projects. It enables AI agents to manage plans, tasks, and integrations via tool calls.25MIT
- FlicenseNot gradedqualityAmaintenanceA local-first MCP server and CLI that gives coding agents structured project memory, task contracts, context packs, backlog workflows, and verification evidence, storing data in reviewable Markdown/YAML with a fast SQLite index.3-
- AlicenseNot gradedqualityDmaintenanceMCP server that adapts, activates, and shares local Agent Skills for runtimes like OpenAI Agents SDK and Claude Code, enabling dynamic discovery and shareable HTML/image artifacts.36 npm2MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server provides a local-first control plane for coding agents, enabling task routing, contract management, and shared learning across multiple AI vendors via markdown files.5MIT
TDQS
Scored across 23 tools
Each tool targets a distinct entity or action (profile, blueprint, use case, etc.), with clear descriptions that differentiate similar operations like get_blueprint (summary) vs download_blueprint (full data). No two tools appear to overlap in purpose.
All 23 tools follow a consistent verb_noun pattern in snake_case (e.g., create_business_profile, list_blueprints, sync_implementation_state). The naming is predictable and easy to navigate.
23 tools is slightly above the typical well-scoped range of 3-15, but the complexity of managing blueprints, profiles, use cases, implementation plans, and progress tracking justifies the count. Each tool serves a necessary function.
The tool set covers the full lifecycle from profile creation to implementation tracking, including financial recalculation and metric reporting. Minor gaps like missing delete operations exist, but the core workflow is well-supported.