awwwards-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_sitesA | Search award-winning websites on Awwwards. Returns site cards with inline screenshots, live URLs, awards and tags. |
| get_site_detailsB | Get the design DNA of one Awwwards site: color palette, technologies, design elements, awards, description and inline screenshot. |
| get_site_elementsA | Get the design-element highlights of one Awwwards site: component-level visuals (3D models, video content, mobile layouts, microcopy) with poster images inline and video URLs. |
| list_categoriesA | List the filter taxonomy available on Awwwards: color hexes and tag/technology slugs usable with search_sites. |
| capture_live_siteA | Take a fresh full-page screenshot of a live website URL using a headless browser. Requires the optional playwright dependency. |
| analyze_page_structureA | Extract a page's section band map (tag, label, background color, offset, height per band) via a headless browser. Works on live URLs and file:// paths — use it to compare a reference site's structure against your local build. |
| record_site_motionA | Record a short motion-through video of a live website — preloader, scroll-triggered and hover/cursor animations — and return an inline filmstrip JPEG plus the .webm path. Requires the optional playwright and ffmpeg-static dependencies. |
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 7 tools
Most tools target distinct resources: search, site details, elements, categories, and three browser actions. The only potential confusion is get_site_details vs get_site_elements, but their descriptions clearly separate site-level design DNA from component-level highlights.
All tools follow a consistent verb_noun pattern (get_site_details, search_sites, list_categories, capture_live_site, analyze_page_structure, record_site_motion). No mixing of conventions or vague verbs.
Seven tools is well-scoped for an Awwwards-focused server that covers search, lookup, taxonomy, and live-site inspection. Each tool has a clear role without redundancy.
The surface covers the full workflow: discover sites via search and categories, inspect site details and elements, then capture/analyze/record live sites for comparison. No obvious gaps for the stated inspiration and design-analysis purpose.