Authorization notice. Awwwards MCP is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA frontend developer who has a draft page and needs an objective check that it matches the structure and motion of a chosen reference.
The problemEyeballing a rebuild against a reference misses section spacing, scroll triggers, and easing differences.
The outcomeA 0 to 100 score with a pass, warn, or fail verdict and evidence lines, plus a list of band and motion differences to fix.
What you need first
- Node.js 22.13 or newer (check with `node -v`)
- An MCP-compatible coding agent such as Claude Code, Codex CLI, OpenCode, or Cursor
- No API key or account is needed for the core search tools
- Playwright, as linked from the README, for the live-capture, scroll-map, and verify tools
Steps
- Run
claude mcp add awwwards -- npx -y awwwards-mcpand install the Playwright setup linked in the README. - Ask the agent to run analyze_page_structure on the reference URL and on your local file:// build to compare section bands.
- Run verify_build with the reference URL and your build to get the score, verdict, and evidence lines.
- Fix the lowest-scoring bands or motion differences the evidence lines name.
- Re-run verify_build until the verdict is pass.
Prompt for your agent
Use the awwwards-mcp server to run verify_build comparing my local build at <build file:// path> against the reference <reference URL>. Expected output: a 0 to 100 score, a pass, warn, or fail verdict, and evidence lines naming each band or motion gap. Verify the score changes after you apply one fix and re-run the check.
Caveat. Verification needs Playwright and compares structure and motion fingerprints only, so a passing score does not confirm visual polish or content quality.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page