mcp-software-design
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_catalogA | List the catalog of software-design concepts, optionally filtered by kind. Returns each concept's slug, name, category, and one-line summary. |
| explain_conceptA | Return an authoritative explanation of one design principle or GoF pattern: intent, when to use it, trade-offs, participants, and related concepts. Accepts a slug, full name, or alias (e.g. "SRP", "factory"). |
| scaffold_patternA | Generate a language-agnostic pseudo-code skeleton for a GoF pattern, showing its participants and how they collaborate. Optionally rename roles to your domain (e.g. Product -> Notification). Translate the result into your target language. |
| check_smellsA | Scan a code snippet for heuristic design smells (long method, large class, long parameter list, deep nesting, duplication, large file). Each finding maps to the principle it hints at plus a suggested refactor. HEURISTICS ONLY — hints, never verdicts; a clean run does not certify good design. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_design | Prime the model to review a code snippet against SOLID/OOP/DRY and the GoF patterns, grounded in this server's catalog and check_smells output. Assumes the client lets its model call this server's tools; where it doesn't, the model reviews from the inlined code alone. |
| apply_pattern | Prime the model to refactor a snippet to apply a named GoF pattern, using the server's scaffold_pattern + explain_concept as reference. Assumes the client lets its model call this server's tools; where it doesn't, the model works from the inlined code and pattern name alone. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| principles | SOLID, the OOP pillars, DRY, KISS, YAGNI, and related heuristics. |
| patterns | The 23 GoF patterns, grouped creational / structural / behavioral. |
| smells | What the check_smells tool detects, its thresholds, and caveats. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qwertymuzaffar/mcp-software-design'
If you have feedback or need assistance with the MCP directory API, please join our Discord server