Pixasso MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pixasso_discover_intentB | Initiate adaptive intent discovery for a frontend project across the 16 pillars and generate tailored popup questions. |
| pixasso_search_referencesB | Search across all 20 Pixasso design reference catalogs, 11 templates, and the 16 frontend pillars. |
| pixasso_fetch_referenceA | Fetch and deconstruct a live reference website server-side. Extracts page title, meta description, heading structure (h1-h4), visible links, and readable text content. Detects client-rendered SPAs (Framer, Webflow, React shells) and flags unrendered content rather than hallucinating. NOTE: Does not extract computed CSS (colors, rendered fonts); use headless browser tools or user screenshots for visual styling. |
| pixasso_generate_genomeB | Validate design decisions and compile a machine-readable design-genome.yaml specification. |
| pixasso_generate_brainB | Build a Graphify-style Mermaid visualization mapping design decisions and Task DAG execution state. |
| pixasso_audit_designB | Audit HTML, JSX, or CSS against generic AI clichés, accessibility guidelines, and the 16-pillar rubric. |
| pixasso_generate_test_planB | Generate an automated multi-viewport testing matrix (390px, 768px, 1024px, 1440px) and overflow detection script. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| intent-discovery | Initiate adaptive intent discovery using the Adaptive Discovery Matrix before generating code. |
| frontend-architecture | Scaffold an end-to-end frontend engineering architecture across all 16 foundational pillars. |
| design-critique | Conduct a rigorous 5-pillar design and code quality audit to detect generic AI tropes and a11y flaws. |
| typography-direction | Define an intentional typography system (display, serif, monospace) using modular math scales. |
| interface-qa | Generate an automated multi-viewport testing matrix (390px, 768px, 1024px, 1440px) and overflow checks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Reference: Frontend Architecture Pillars | Complete guide covering the 16 foundational pillars of frontend engineering and design craft. |
| Reference: Discovery Framework & Adaptive Matrix | Adaptive Intent Discovery protocol and project archetype inquiry matrix. |
| Reference: Design Genome Persistence | Structured persistence of tokens, constraints, and epistemic design states. |
| Reference: Design Brain Visualization | User-visible Graphify-style Mermaid maps of design decisions and Task DAG state. |
| Reference: Typography System & Mathematics | Typeface.fyi integration, modular scales, line lengths, and optical pairings. |
| Reference: Typography Discovery Protocol | Deep inquiry into typographic hierarchy, headline personality, and body readability. |
| Reference: UI Component Libraries | Aceternity UI, Originkit, Dialkit Agent, RareUI, Libraries.dev, React Bits, and shadcn. |
| Reference: Creative Coding & WebGL 3D | Spline 3D browser automation, ThreeUI, Glass Samasante optical shaders, Canvas 2D, and WebGPU. |
| Reference: Motion & Animation Systems | Transitions.dev, SceneAI.art prompt recipes, Motion.dev, GSAP, and spring physics. |
| Reference: Sound & Sensory Design (UISFX) | Web Audio API micro-interactions, subtle feedback cues, and auditory tactile craft. |
| Reference: Interface Testing & QA Automation | Multi-viewport testing (390px, 768px, 1024px, 1440px), DOM overflow detection, Lighthouse, and a11y. |
| Reference: Inspiration Galleries | Curated.design, Recent.design, VibeUI, DesignPrompts.dev, and portfolio benchmarks. |
| Reference: Anti-Patterns & Critique Rubric | Elimination of generic AI design tropes and 5-pillar objective critique framework. |
| Reference: Art Direction & Spatial Dimensions | 2D vs 2.5D vs 3D criteria, visual worlds, lighting, and surface materiality. |
| Reference: Agent Orchestration & Tool Registry | Agent Harnesser architecture, subagent delegation, and MCP tool coordination. |
| Reference: Task Graph & Dependency DAG | Dependency-aware DAG management, task packets, and parallel execution pipelines. |
| Reference: Tool Registry & Capability Tags | Catalog of agent tools, MCP servers, and specialized capability mapping. |
| Reference: Contradiction Resolution | Systematic framework for resolving conflicting design goals and technical constraints. |
| Reference: Generative Assets & Tools | Procedural SVGs, visual diffusion art direction prompts, and asset workflows. |
| Reference: Live Case Studies | In-depth architectural deconstructions of industry-leading digital craft benchmarks. |
| Template: Component Implementation Spec | Production component specification including accessibility, props, and states. |
| Template: Interface Test Plan | Multi-viewport testing matrix, DOM overflow checklist, and Lighthouse goals. |
| Template: Design Brain Template | Mermaid decision map and live Task DAG status template. |
| Template: Design Brief Scaffold | Structured project intake document capturing goals, audience, and constraints. |
| Template: Design Critique Rubric | Scorecard evaluating designs across the five objective craft pillars. |
| Template: Design Genome YAML Schema | Machine-readable design tokens, epistemic states, and constraints schema. |
| Template: Design Mode Specification | Aesthetic mode definition binding philosophy to visual tokens. |
| Template: Project State Schema | YAML tracking active phase, capability registry, and handoff state. |
| Template: Task Graph YAML Schema | Machine-readable DAG definition with agent assignments and dependencies. |
| Template: Typography Specification YAML | Tokens for mathematical type scales, line heights, and font pairings. |
| Template: Agent Task Packet | Context-isolated assignment packet for specialist subagents. |
TDQS
Scored across 7 tools
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.
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.
Seven tools form a well-scoped set for a frontend design assistant, covering discovery, research, generation, auditing, and testing without redundant or trivial entries.
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.