design-pattern-mcp
Related Servers
Alternatives to design-pattern-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding agents structured access to a project's architecture, rules, modules, and technical decisions.MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables users to store and retrieve personalized coding patterns, serving as a persistent memory layer for LLM agents. It allows AI models to generate code and refactor projects according to a user's specific styles, technologies, and established development conventions.71MIT
- AlicenseAqualityDmaintenanceAn MCP server that allows coding agents to look up contextual rules and patterns on demand, providing just-in-time guidance for specific tasks like writing tests or authoring UI.28MIT
- AlicenseBqualityDmaintenanceMCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.394MIT
- AlicenseAqualityAmaintenanceAn MCP server that helps AI coding agents navigate codebases, discover reusable functions, and inspect callers before making changes.88MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.10 npmMIT
TDQS
Scored across 13 tools
The main design tools form a closely related pipeline, but the descriptions explicitly distinguish analyze_design (analysis only), generate_design (materialize applications), and select_design_patterns (full generated design). The background job tools and prompt/resource tools are clearly separate, though the pipeline overlap still creates some risk of misselection.
All tool names use a consistent snake_case verb_noun pattern: select_design_patterns, analyze_design, generate_design, evaluate_design, list_design_patterns, get_design_pattern, submit_design_job, get_design_status, cancel_design, list_prompts, get_prompt, list_resources, read_resource. The only minor deviation is cancel_design omitting 'job', but the convention remains clear throughout.
With 13 tools, the server is well within a reasonable range for a focused design-pattern assistant. The set covers the design pipeline, catalog lookup, asynchronous job control, and generic prompt/resource access without obvious bloat.
The server covers the core lifecycle: analysis, generation, evaluation, combined selection, catalog listing/retrieval, and background job submission/status/cancel, plus prompt and resource access. Minor gaps exist, such as no tool to list active background jobs and no pattern mutation operations, though these are likely out of scope or workable from provided job IDs.