DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to get alerts when new award winners match your watched studios or tags with Awwwards MCP

Poll new winners and watch studios or tags, then report only what changed since the last check.

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 designer or agency lead who tracks specific studios or design tags and wants fresh references without browsing the Awwwards listing every day.

The problemChecking the award listing by hand is slow, and it is easy to miss a new winner in a tag you care about.

The outcomeA list of new winners and per-watch NEW deltas, with each new winner's elements made searchable immediately.

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

  1. Run claude mcp add awwwards -- npx -y awwwards-mcp.
  2. Ask the agent to call new_winners once to seed the baseline and dump the current listing.
  3. Ask the agent to add watches over studios, tags, or specific sites using watch_site.
  4. Run new_winners again later to report the delta since the baseline.
  5. Run watch_site with the list action to see NEW since last check per watch.

Prompt for your agent

Use the awwwards-mcp server to call new_winners to set a baseline, then add a watch_site entry for the tag <tag name>. Expected output: a list of new winners and per-watch NEW since last check deltas. Verify that a second new_winners call reports only winners that were not in the first listing.

Caveat. The watch list reports from the cached listing and never fetches on its own, so new_winners or search_sites must run to refresh it.

Share: 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