Skip to main content
Glama
Erebuzzz

Pixasso MCP Server

by Erebuzzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Pixasso MCP Server

No user-submitted related servers found.

    Related Servers

    • frontend-stack

      Suhaib5333
      A
      license
      A
      quality
      C
      maintenance
      Gives AI coding agents a ten-phase frontend design pipeline (audit, style direction, build, review, verify, perf, brand) with an exclusive style menu. Its verify_page tool loads a URL in a real Playwright browser at mobile and desktop viewports and returns screenshots, ARIA snapshots, console errors, failed requests, horizontal-overflow offenders, axe-core violations, and pointer type.
      3
      MIT
    • Layoza by layoza

      Layozaofficial

      layoza
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to act like a senior UI/UX team by reading an existing site's design DNA and tokens, proposing distinct art directions and motion mechanics that fit the brief, and validating changes in a live headless Chromium browser. Provides per-element accessibility and performance auditing (WCAG 2.2 contrast, focus, clipping, phone-menu behavior, LCP/CLS) at multiple viewport widths, plus baseline capture, before/after comparison, and one-command rollback for safe redesigns.
      1
      MIT

    • vibecraft-mcp

      satyamuiux-byte
      A
      license
      A
      quality
      C
      maintenance
      Provides deterministic UI/UX intelligence and systems performance auditing tools for AI coding agents, enabling generation of accessible, well-designed React/Tailwind interfaces and elimination of backend anti-patterns like N+1 queries and sequential waterfalls.
      7
      MIT
    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.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct action and target: discovering intent, searching vs. fetching references, generating genome vs. brain vs. test plan, and auditing design. The descriptions make boundaries explicit, so an agent can reliably select the right tool.

    Naming Consistency4/5

    All tools use a consistent pixasso_verb_noun pattern with snake_case. A minor deviation exists in the noun form for reference tools (search_references plural vs. fetch_reference singular), but overall the convention is predictable.

    Tool Count5/5

    Seven tools form a well-scoped set for a frontend design assistant, covering discovery, research, generation, auditing, and testing without redundant or trivial entries.

    Completeness4/5

    The surface covers the core design workflow from intent discovery through reference research, specification, visualization, auditing, and test planning. However, there is no tool to directly generate or scaffold frontend code/design assets, and visual styling extraction is explicitly delegated to external tools—minor gaps the agent can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources