design-knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP server bind address | 0.0.0.0 |
| PORT | No | HTTP server port | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_principlesA | Get design, UX, and conversion principles from 12 Frontend Masters courses. Returns structured knowledge from a specific domain or all domains. |
| audit_conversionA | Audit page text/description against the 4 psychological pillars of conversion: objections, cognitive load, trust, and speed. Returns scored feedback with specific improvements. |
| audit_contentB | Audit content quality: headlines, structure, copywriting principles, scannability, and value proposition clarity. |
| audit_visualA | Get visual design feedback based on layout, color, typography, and imagery principles from Sarah Drasner's Design for Developers course. |
| check_accessibilityB | Check design accessibility: color contrast, typography readability, and inclusive design principles. |
| get_testing_planA | Get recommended testing methods based on project phase. Returns specific methods, tools, and how-to guidance. |
| get_ia_recommendationsB | Get information architecture guidance: top task analysis, card sorting, tree testing, and navigation best practices. |
| get_design_processA | Get guidance for a specific phase of the design process: discovery, prototyping, build, or live. Includes checklist and deliverables. |
| get_stakeholder_tipsA | Get advice for handling stakeholders: presenting design, managing feedback, dealing with objections, and handling scope creep. |
| generate_headlinesB | Generate headline formulas based on emotional triggers from Paul Boag's conversion psychology framework. |
| recommend_layoutA | Get layout recommendations based on content type: grid system, CSS approach, composition principles, and reading patterns. |
| build_color_paletteA | Generate a color palette with HSL values and CSS variables based on mood and brand keywords. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct aspect of design: principles, audits (conversion, content, visual, accessibility), testing, IA, process, stakeholders, and generators (headlines, layout, color). There is no significant overlap; even the three audit tools differ in focus.
All tools follow a consistent verb_noun pattern: get_*, audit_*, check_*, generate_*, recommend_*, build_*. The verbs are specific and predictably describe the action, making the tool set easy to navigate.
12 tools is within the ideal 3-15 range for a design knowledge server. Each tool covers a meaningful capability without redundancy, and the count feels well-scoped for the domain.
The surface covers a comprehensive range of design knowledge: principles, audits across conversion/content/visual/accessibility, testing, IA, process, stakeholder advice, and generative tools for headlines, layout, and color. No obvious gaps for the stated purpose.