AestheticForge MCP
Provides source intelligence for CSS tokens, styles, typography, spacing, imports, and component duplicates, and compiles semantic token CSS for light/dark colors and reduced-motion durations.
Supports source intelligence for Inertia dependency and file conventions within the inspected project.
Supports source intelligence for Laravel Blade templates and related framework file and dependency conventions.
Offers an optional Lighthouse CLI integration for performance and network auditing when explicitly enabled with allowNetwork: true.
Supports source intelligence for Nuxt project structure and framework-specific file conventions.
Supports source intelligence for React source files and framework conventions, enabling targeted framework-specific source changes.
Supports source intelligence for Svelte and SvelteKit file and dependency conventions.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
AestheticForge MCP
A local MCP server for evidence-based interface engineering. It inspects actual project files, compiles client-authored design specifications and tokens, applies controlled source changes, and verifies running pages with Playwright, axe-core, PNG comparisons, and browser timing data.
The AI coding client supplies creative decisions and framework-specific source. The server supplies explicit contracts, safe operations and measurable evidence. It does not pretend a generic text response is a finished interface or that automated checks prove beauty, usability, or complete WCAG conformance.
Install
Requires Node.js 20.20+ and npm. Browser tools need Chromium or compatible Chrome. No hosting, account, or paid service is required.
git clone https://github.com/2peng23/aestheticforge-mcp.git
cd aestheticforge-mcp
npm ci
npx playwright install chromium
npm run build
npm test
npm run smokenpm install also works and builds through prepare. On Linux, Playwright may need system packages: npx playwright install --with-deps chromium.
node /absolute/path/aestheticforge-mcp/dist/server/cli.js --root /absolute/projectAdd --root /absolute/artifacts for a separate existing output directory. All roots must already exist. No root is implicitly granted. To use installed Chrome, set AESTHETICFORGE_BROWSER_PATH to its executable. Only exact explicitly granted remote origins can be loaded with --origin https://example.com. Browser subresources are restricted to the selected page origin and startup-authorized origins.
The executable npm package is prepared for future npx -y aestheticforge-mcp distribution. That command requires publication first; it has not been tested against the public package name.
Related MCP server: Design GL
What works
All 60 requested tool names are registered, with Zod input validation, structured results and MCP errors. See tool reference for exact scope and input schemas generated from the running registry.
Source intelligence for HTML/CSS/JS, React, Next, Vue, Nuxt, Svelte/SvelteKit, Laravel Blade and Inertia dependency/file conventions. Discovery is static and heuristic; it does not execute application code or evaluate dynamic routers.
Actual CSS tokens, styles, typography, spacing, imports and component duplicates. Semantic token CSS supports light/dark colors and reduced-motion durations.
Design and component specifications compiled from explicit product facts, client-selected direction, rationale, contracts and state graphs. Creative judgment remains with the AI client or human.
Source writes supplied by the AI client, default dry-run, existing-file hash preconditions and atomic replacement. No arbitrary project command execution or automatic framework migration.
Real screenshots, width matrices, overflow, candidate control overlap, touch target dimensions, forms, headings, landmarks, keyboard focus and explicit interaction/assertion steps.
Actual axe-core WCAG A/AA rules, normal/reduced-motion animation evidence, resource/navigation/paint timings and observed layout shifts. Geometry and computed-style checks are evidence, with documented limits.
PNG pixel differences, optional diff images and evidence reports. Screenshots mask all inputs and explicitly private content; use synthetic data throughout.
Optional actual Lighthouse CLI integration with explicit
allowNetwork: true. It is not bundled: Use Node22.19+ for the server and install current Lighthouse13.6 separately. Review limitations before using it.
Demonstration
npm run demoFor installed Chrome on macOS:
AESTHETICFORGE_BROWSER_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" npm run demoThe demonstration starts an isolated local server, discovers the sample app, captures baseline screens, proves narrow-screen overflow and an unlabeled form field, compiles a project-specific direction, applies a hash-checked correction, runs eleven viewport widths, runs axe, saves before/after diffs and tests the note-saving interaction. It restores the sample source in finally and saves results under artifacts/<timestamp>/acceptance-report.json. The deliberate baseline defects are retained for repeatability.
MCP clients
See client configurations for Codex, Claude Code, Cursor and VS Code. Configurations are documented against official references and validated by an SDK stdio integration test; GUI client installation has not been exercised. Stdout is reserved for MCP traffic. Diagnostics use stderr.
Verification and limits
Run npm run build, npm test, npm run smoke, npm run demo, and npm pack --dry-run. No remote publication occurs. Browser tests have been run on macOS Chrome; Windows/Linux, other browsers, client applications, every framework compiler, screen readers, physical mobile devices are not claimed tested. Lighthouse13.6 was separately exercised on the local sample under Node25.
Security · Methodology and limitations · Contributing · API sources
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Serves your design system and coding standards to coding agents, so they stop guessing.
Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow.
Live React design-system APIs, patterns, and code validation so AI agents build real UI, not slop.
Website checker for AI coding agents. Measures your site in a real browser, with evidence.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides coding agents with local tools to inspect project UI inventories, propose and compare visual direction boards, compile versioned design contracts and DTCG tokens, retrieve section-specific blueprints, and audit running interfaces with browser evidence including screenshots, accessibility findings, and overflow measurements.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to audit rendered web pages for design and UI defects by measuring geometry, styles, contrast and motion in a local browser and judging them against evidence-tiered rules. Findings come back as short, fixable items expressed in the project's own design tokens, while only sanitized numeric measurements leave the machine.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.91 npm3MIT
- AlicenseBqualityCmaintenanceEnables AI agents to build and audit web UIs by serving a fixed workflow and rule-priority guide, running deterministic static linting of source, rendering pages headlessly at multiple widths for screenshots and accessibility snapshots, and gathering element-level design feedback. All output is written only to a local log folder, leaving project files untouched and external network access blocked by default.6MIT