Skip to main content
Glama
INSANE0777

awwwards-mcp

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to awwwards-mcp

No user-submitted related servers found.

    Related Servers

    • A1 Gallery MCP Server

      bryntay
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides curated real website design references with structured JSON data on type, spacing, palette, and layout. Enables AI agents to search, browse, and analyze over 1,000 sites and their sections.
      1
      MIT

    • plate

      ohad6k
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to capture and inspect running projects, resolve real assets from free sources, and check source for design tells, providing an evidence loop for improving websites, games, and motion.
      10
      1
      MIT

    • Inspo MCP

      Nutlope
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to search and retrieve real production websites, their design systems, and reference components over MCP, so they can study design patterns before writing UI.
      239
      MIT

    • websight

      h34tsink
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to see, analyze, and visually verify web page changes through pixel-perfect diffing, theme extraction, layout analysis, and interactive element detection.
      19 npm
      MIT

    • MotionDesign MCP

      Pdroinho
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to architect and build Awwwards-level websites with spring physics, design systems, React 19 templates, and HD visual inspection.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources