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_sitesB | Search award-winning websites on Awwwards. Returns site cards with inline screenshots, live URLs, awards and tags. |
| get_site_detailsA | Get the design DNA of one Awwwards site: color palette, technologies, design elements, awards, description and inline screenshot. |
| compare_sitesA | Compare the design DNA of 2–3 Awwwards sites: titles, live URLs, palettes, technologies, elements, awards and jury scores. Text only; missing details are fetched and cached. |
| get_index_statusA | Read offline index status: cached site count, progress, last successful finish and error, lock state and freshness. No live requests. |
| 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. |
| search_elementsA | Search Awwwards' curated element gallery — award-grade UI components (footers, menus, loaders, transitions, micro-interactions…). Usage: pass query text and at most one of category/stack; every result links back to its source element page and parent project. |
| get_elementA | Get one Awwwards element in full: title, author, built-with stack, media URLs, related elements and the parent award-winning project. Use search_elements first for ids. |
| 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. |
| get_motion_dnaA | Get the Motion DNA of a website: animation stack, ScrollTrigger/pin/scrub counts, easing vocabulary and duration distribution. Serves the corpus first; live-captures unseen URLs (headless browser required). |
| search_motionA | Search captured Motion DNA records: find sites that pin sections, scrub scroll-driven animation, or run a given animation library. Corpus only — live-capture happens via get_motion_dna. |
| new_winnersA | Poll today's new Awwwards winners as a delta against the previous poll: new-entrant cards since the last call (first call seeds the baseline and reports no delta). Poll daily for a winners feed; pairs with watch_site for structured monitoring. |
| watch_siteA | Longitudinal watchlist over Awwwards listings: track a studio (e.g. 'ToyFight'), a tag/technology slug (e.g. 'webgl'), or a site URL-slug for changes and new entries. add/list/remove; the delta is reported by watch_site list after new_winners or search_sites refreshes the listing. |
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 15 tools
Each tool targets a distinct resource/action: site search/details/compare, element gallery, motion DNA/search, live capture/structure/motion recording, and monitoring. Overlaps such as the search_* tools are separated by domain, and descriptions clarify outputs. No pair appears interchangeable.
Names are consistently snake_case and mostly verb_noun, making actions predictable. The one minor deviation is new_winners, which is a noun phrase rather than verb_noun, but the overall convention is stable.
15 tools is within a reasonable upper bound for a multi-capability design-research server. Each tool maps to a distinct capability such as search, detail, compare, live capture, motion, or monitoring, so none feels redundant.
Core lifecycle for design research is well covered: discovery, detail, comparison, elements, categories, live capture, motion analysis, and watchlist add/list/remove. Minor gaps remain, such as no dedicated new-elements feed or explicit element-category listing, but agents can work around them.