Design Style MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESIGN_STYLES_PATH | No | Override path to the design-styles data directory | ./design-styles |
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 |
|---|---|
| recommend_styleA | Recommend a design style based on brand context, campaign objective, and target demographic. Returns a top match with reasoning and alternatives. No AI inference — uses deterministic scoring against style characteristics. |
| get_styleA | Retrieve structured design style tokens for AI content generation. Returns name, description, color palette, typography, mood, visual directives, and negative prompt sections extracted from the style's prompt file. Valid slugs: academia, art-deco, bauhaus, bold-typography, botanical, claymorphism, cyberpunk, enterprise, flat-design, industrial, kinetic, luxury, material, maximalism, minimal-dark, modern-dark, monochrome, neo-brutalism, neumorphism, newsprint, organic, playful-geometric, professional, retro, saas, sketch, swiss-minimalist, terminal, vaporwave, web3 |
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 2 tools
Both tools have clearly distinct purposes: get_style retrieves details for a known style, recommend_style suggests a style based on context. No overlap.
Both tool names follow the verb_noun pattern (get_style, recommend_style) consistently, making them predictable.
With only 2 tools, the server is minimal but still covers the core functionality for its narrow domain. A list tool would be useful but not mandatory.
Covers retrieval and recommendation, but lacks a tool to list all available style slugs programmatically, which is a notable gap since get_style requires a valid slug.