Skip to main content
Glama
rikoarik

awsm

by rikoarik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to awsm

No user-submitted related servers found.

    Related Servers

    • @designjs/mcp-server

      rubychilds
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI coding agents to read and write to a local-first HTML/CSS design canvas, bridging visual design and code generation.
      1
      MIT

    • s-gw MCP server

      sgateway
      A
      license
      B
      quality
      A
      maintenance
      A local stdio MCP server that enables coding agents to discover credential handles and create scoped action requests with local approval and sanitized output.
      7
      131 npm
      15
      Apache 2.0
    • Identity Forge MCP by KasayoDotCom

      Identity Forge MCPofficial

      KasayoDotCom
      A
      license
      A
      quality
      A
      maintenance
      MCP server for design kits and brand workflows. Coding agents can browse and apply design systems, create brand projects, and research names, domains, and EUIPO marks.
      61
      77 npm
      MIT

    • Kontrol

      B-A-M-N
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that enables AI coding agents to read, edit, search, and run code in local projects with human review loops and policy controls.
      MIT

    • cove-sensory-mcp

      moonlin1213
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets an Agent use configured multimodal providers to inspect images, video, audio, and music files, acting as a sensory layer for text-only LLMs.
      116
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (find_icons vs get_icon vs save_icon_set, palette vs check_contrast, bridge_list vs bridge_call). A few overlaps exist: find_design_assets aggregates find_icons/find_images, and review_ui composites capture_ui_screenshots and audit_ui_page, so an agent must decide between the granular and combined tools. Descriptions do clarify the boundaries reasonably well.

    Naming Consistency4/5

    The dominant pattern is snake_case verb_noun (find_icons, get_icon, save_icon_set, check_contrast, inspect_ui_project), applied consistently across the majority of tools. Minor deviations exist: 'palette' is a bare noun and 'serve' a bare verb, and the bridge_list/bridge_call pair uses a prefix style rather than verb_noun. Readable and predictable overall.

    Tool Count3/5

    23 tools is on the heavy side for a design/asset workflow server and sits in the borderline 16-25 band. Most tools do earn their place given the broad domain (icons, images, assets, color, fonts, FigCraft handoff, screenshots, audits, bridges), but the surface is large enough to feel sprawling and increases selection burden. Scoping down or merging composite tools would help.

    Completeness4/5

    The domain of design-asset and UI-review workflow is broadly covered: discovery (icons, images), creation (draw_icon, make_asset), styling (palette, google_font, check_contrast), preview (serve), FigCraft ingestion (prepare_web_handoff, sync_figcraft_assets, extract_design_tokens), and UI verification (capture/compare/audit/review). Minor gaps exist: no way to list or clean up previously saved assets, and no image optimization step. Core workflows are not blocked.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources