Skip to main content

Search the portfolio

33 matches · showing 7

11 choices. A body of work. A web of ideas.

Skip to content
Evelyna Bellamy
Auto · Daylight
Time of day

Following your local clock · Daylight

Warm ivory · charcoal · open sky

Local time, no location access. Choose a stop to keep that atmosphere.

A more
curious
tomorrow

Ideas / language / human contextIdeas / systems / human context
← The journal

Translation, Actually /

Instruments, Not Oracles: Ten Design MCPs That Earn Their Keep

Language models are fluent predictors of plausible syntax, not instruments of measurement. A field guide to the ten Model Context Protocol servers that replace guesswork with real craft in design and frontend work.

Graphite engraving of proportional dividers, an optical glass prism, and porcelain pigment wells crossed by translucent Prussian-blue drafting planes.

A model predicts
the syntax.
An instrument
measures light.

01 / Instruments, not oraclesIllustration

There's a quiet comedy happening in frontend engineering right now. We take a language model — a system trained to predict the most statistically probable next token in a sequence of text — and we ask it to behave like a typographer, a color scientist, and an accessibility engineer all at once. Then we act surprised when it hands us a button with light-gray text on a slightly-less-light-gray background and assures us, with total confidence, that it passes contrast.

The model isn't lying, because lying requires knowing the truth. It's doing what it was built to do: performing the syntax of competence. It has seen thousands of stylesheets where a hex code follows a colon, so it produces a hex code that looks right in the file. It has no eyes to see the rendered surface, no ruler to measure the viewport, and no math to calculate how human cones and rods perceive luminance.

That gap — between plausible syntax and physical reality — is why the Model Context Protocol (MCP) actually matters for design work. Not because agents need more buzzwords, and certainly not because every API on earth deserves a wrapper. It matters because an MCP server lets you hand a language model an instrument. Instead of asking an oracle to guess what a color mix or a DOM tree looks like, you give a carpenter a caliper and tell them to measure before they cut.

FIG. 01 / PLAUSIBLE SYNTAX VS. MEASURED LIGHTChromatic Assay

01 · Subtractive Pigment Mixing

Ultramarine + Yellow Ochre

Unassisted models average RGB channels into gray slate. mix_pigments inverts reflectance via Kubelka–Munk K/S = (1 − R)² / 2R.

#1B3F8BUltramarine
#D49B27Yellow Ochre
#786D59
Raw LLM GuessLinear RGB mean (mud)
#436B3C
Chromologium MCPKubelka–Munk scatter
400 nm535 nm peak700 nm

02 · Tonal Ladder & APCA Polarity

Monotonic OKLCH vs. Guessed Hex

generate_accessible_scale spaces lightness evenly for human photoreceptors and pre-scores WCAG 3 APCA Lc.

Unassisted LLM hex steppingUneven ΔL · Hue drift
Chromologium OKLCH 50–900Constant hue · APCA verified
948774584162768795101
Aa — Caption specimenLc 29 · Fails body
Aa — Caption specimenLc 82 · Passes body
02 / Why prose cannot substitute for a perceptual modelKubelka–Munk + OKLCH + APCA

The Context Window Is a Worktable, Not a Warehouse

If you browse any of the giant MCP directories that have sprung up over the past year, you'll find five thousand scraped repositories sorted by GitHub stars and very little editorial judgment. Treating your agent configuration like an all-you-can-eat buffet is a trap. Every tool schema you mount into a session occupies space on the worktable. Bolt thirty servers into your configuration, and the model spends half its attention just reading the manual.

A good toolkit is defined as much by what you leave out as by what you include. What follows isn't an exhaustive catalog of everything with 'UI' in its README. It's the ten design and frontend MCP servers that actually earn their place in the context window — each one chosen because it fixes a specific blind spot where raw language models reliably guess wrong.

FIG. 02 / TOPOLOGY OF THE WORKTABLEThree Concentric Rings
OUTER RING · VECTOR, PATTERN & SPATIALMIDDLE RING · BEHAVIORAL & SYSTEMIC GUARDSINNER RING · DAILY VERIFICATION TRIADCONTEXT WINDOW.mcp.json worktable01 · Figma MCPIntent graph02 · Chrome DevToolsComputed DOM03 · ChromologiumOKLCH · APCA · K/S04 · Playwright320px & focus05 · StorybookShared vocabulary06 · Shadcn UIFocus primitives07 · Axe A11yWCAG / ARIA tree08 · 21st.devUI references09 · SVGL / IconifyExact vectors10 · Blender / Three.js3D scene graph
03 / Mount only the ring your current task requiresContext budget architecture · Logos by Logo.dev
Isometric graphite and Prussian-blue watercolor study of a drafting worktable with translucent vellum, woven cloth, and contour relief.
04 / The worktable, not the warehouseIllustration

Sight, Structure, and Chromatic Truth

01Figma logo

Figma MCP

figma.com ↗

Reading the blueprint instead of squinting at a screenshot.

A screenshot is a flattened rumor of a design system. When you paste a PNG of a mockup into a chat window, you force the model to reverse-engineer spacing tokens, auto-layout rules, and semantic hierarchy by squinting at pixels. Figma's official MCP server hands the agent the actual structural graph — variables, layout constraints, component boundaries, and token names — so translation starts from authored intent rather than visual guesswork.

Mount Figma MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add --transport http figma https://mcp.figma.com/mcp
"figma": { "url": "https://mcp.figma.com/mcp" }
02Chrome DevTools logo

Chrome DevTools MCP

developer.chrome.com ↗

Closing the loop with the rendered DOM.

Writing CSS without inspecting the live browser is like mixing audio with the studio monitors turned off. A stylesheet is only a proposal; the browser's layout engine has the final vote. The Chrome DevTools MCP lets an agent inspect computed styles, measure layout shifts, read console diagnostics, and verify what actually landed on the glass instead of assuming its first draft worked.

Mount Chrome DevTools MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
"chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"] }
03Chromologium logo

How interfaces feel: sourced materials, chromatic physics, tactile surfaces, and portable tokens.

I built Chromologium's MCP server (https://chromologium.com/connect) because unassisted models flatten everything into the same weightless SaaS defaults — guessing hex ramps, averaging pigments into gray mud, and confusing a pretty reference with a legible interface. Chromologium exposes twenty-five deterministic tools that walk the archive's full Source-to-Interface method (compose_material_study): grounding decisions in 177 mapped places and cited material dossiers, weaving zero-JS SVG/CSS cloth drafts and thin-film interference fringes, mixing archival pigments via two-constant Kubelka–Munk scattering (mix_pigments), computing monotonic OKLCH scales and WCAG 3 APCA contrast repairs (generate_accessible_scale, audit_apca_contrast), linting 320px JSX viewport blowouts, and compiling ten dual-mode design systems — spring kinetics included — into CSS, Tailwind v4, W3C DTCG, SwiftUI, Jetpack Compose, and importable Study Cabinet bundles, while keeping documented sources explicitly distinct from contemporary UI interpretations.

Mount Chromologium MCP in Claude Code / Cursor25 tools · Zero API key · Source → Interface ▾
claude mcp add --transport http chromologium https://chromologium.com/mcp
"chromologium": { "url": "https://chromologium.com/mcp" }

Together, Chrome DevTools and Chromologium also close the typographic blind spot that raw models miss most often: optical rhythm and dark-mode halation. Left alone, an agent will happily let body copy sprawl across ninety-five characters per line, scatter rigid pixel media queries where a fluid clamp() scale belongs, and implement dark mode by inverting black text to pure #FFFFFF on #000000 at weight 500. On an emissive OLED panel, bright glyphs bleed into dark grounds — an optical irradiation effect that makes strokes look heavier and jittery. Pairing polarity-aware APCA luminance checks with live computed-style inspection lets an agent cap reading measure around 60 to 70ch, step down dark-surface ink contrast so letters stop halating, and tune optical weight on the actual glass.

FIG. 03 / SAME PROMPT, MEASURED ON THE GLASS
320px viewport specimen0px overflow · Lc 82
② K/S Olive · #436B3C

Lapis & Yellow Ochre Study

② Mineral dispersion ground in linseed binder; measured under D65 daylight illumination.

① Token Rhythm (16px)③ Export DTCG Tokens →
05 / Toggle above to compare unassisted token prediction against the three-instrument loopFigma + Chromologium + DevTools

Behavior, Vocabulary, and Dignity

04Playwright logo

Playwright MCP

playwright.dev ↗

Testing interaction under real viewport pressure.

Most responsive bugs hide in the places nobody resizes a desktop window to check: a 320-pixel mobile viewport, a keyboard-only modal flow, a container stressed by long localized strings. Playwright's MCP server lets an agent drive a real browser across breakpoints, step through focus order with the Tab key, and catch horizontal overflow before a human reader ever hits it.

Mount Playwright MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add playwright -- npx @playwright/mcp@latest
"playwright": { "command": "npx", "args": ["@playwright/mcp@latest"] }
05Storybook logo

Speaking the language your team already agreed to trust.

A design system only works if the codebase actually uses it. Left to its own devices, an agent will happily invent a brand-new card or badge component from scratch every Tuesday. Wiring a Storybook MCP server into your workspace lets the model inspect your existing stories, prop tables, and states first — treating your component library as a shared grammar rather than an optional suggestion.

Mount Storybook MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add storybook -- npx -y @storybook/mcp@latest
"storybook": { "command": "npx", "args": ["-y", "@storybook/mcp@latest"] }
06shadcn/ui logo

Shadcn UI MCP

ui.shadcn.com ↗

Composable structural primitives without reinventing focus traps.

No one should be asking a language model to improvise ARIA roving tabindex, dialog focus restoration, or popover collision math from memory. The Shadcn MCP gives agents direct access to vetted component primitives and registry schemas so the mechanical plumbing of interactive controls starts on solid ground.

Mount Shadcn UI MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add shadcn -- npx shadcn@latest mcp
"shadcn": { "command": "npx", "args": ["shadcn@latest", "mcp"] }
07Deque Axe logo

Axe Accessibility MCP

deque.com/axe ↗

Treating accessibility as infrastructure, not polish.

Sloppy markup isn't compassionate; it just defers the friction onto the person using assistive technology. An Axe-backed accessibility MCP server runs deterministic WCAG and ARIA rules against rendered DOM trees, catching missing form labels, nested interactive elements, and broken landmark hierarchy that look harmless in JSX but fail in a screen reader.

Mount Axe Accessibility MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add axe -- npx -y @axe-core/mcp@latest
"axe": { "command": "npx", "args": ["-y", "@axe-core/mcp@latest"] }

Reference, Geometry, and Spatial Craft

0821st.dev logo

21st.dev Magic MCP

21st.dev ↗

Exploring the adjacent possible of interface patterns.

When you're sketching a new interaction — a command menu, a dense filter bar, a multi-step disclosure — starting from a blank file often pulls the model toward the most average pattern in its training data. The 21st.dev MCP surfaces curated frontend component references that an agent can study and adapt into your own token architecture.

Mount 21st.dev Magic MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add magic -- npx -y @21st-dev/magic@latest
"magic": { "command": "npx", "args": ["-y", "@21st-dev/magic@latest"] }
09SVGL logoIconify logo

SVGL and Iconify MCP

svgl.app · iconify.design ↗

Real vector geometry instead of hallucinated paths.

Ask a raw language model to write an intricate SVG icon or a product logo from scratch, and you will get a surrealist geometry experiment. Bézier curves are coordinate math, not prose. Pairing an icon registry MCP like Iconify or SVGL lets the agent retrieve clean, properly viewBoxed vector paths instead of guessing coordinates in the dark.

Mount SVGL and Iconify MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add iconify -- npx -y iconify-mcp@latest
"iconify": { "command": "npx", "args": ["-y", "iconify-mcp@latest"] }
10Blender logoThree.js logo

Blender and Three.js MCP

blender.org · threejs.org ↗

Stepping off the flat plane.

Not every digital interface wants to behave like a laminated sheet of paper. When work moves into spatial studies, procedural geometry, or physical-digital lighting, scene-graph MCP servers for Blender and Three.js let an agent inspect meshes, shader uniforms, camera frustums, and lighting rigs directly — bridging the gap between code and three-dimensional form.

Mount Blender and Three.js MCP in Claude Code / Cursor.mcp.json & CLI ▾
claude mcp add blender -- uvx blender-mcp
"blender": { "command": "uvx", "args": ["blender-mcp"] }

What Didn't Make the Worktable — and Four Honest Swaps

Stopping at ten wasn't an accident. Half the discipline of an agentic workflow is refusing to install tools that merely launder machine guesswork behind an extra network hop. Three categories get left off my bench on principle: screenshot-to-JSX wrappers that convert flat PNGs into brittle magic-pixel margins while throwing away variable aliases; gallery hex scrapers that pull five trendy swatches off a moodboard with zero OKLCH lightness discipline or dark-mode APCA math; and sixty-tool SaaS mega-servers that dump an entire REST API into your prompt until the model forgets what you actually asked it to build.

What does change from studio to studio is the authoring stack around that core loop. If your team works in open-source SVG/CSS layout instead of Figma, swap #01 for Penpot's MCP server. If you publish motion-heavy editorial or marketing sites directly out of Framer or Webflow, their respective MCP servers step cleanly into the structural slot. And when you're writing against fast-moving specifications — Tailwind v4, CSS Anchor Positioning, View Transitions, React 19 — pairing Upstash's Context7 MCP beside DevTools streams version-pinned documentation so the model stops hallucinating deprecated syntax from two years ago. Swap by stack; don't hoard.

FIG. 04 / CURATION BOUNDARIES & THE ADJACENT BENCH3 Rejections · 4 Stack Swaps
REJECT · 01Laundered guesswork

Screenshot-to-JSX Wrappers

Converts flat PNGs into magic-pixel margins and invented hex literals while discarding variable aliases and Auto Layout rules.

REJECT · 02No perceptual math

Trend-Gallery Hex Scrapers

Scrapes five decorative swatches off moodboards with zero OKLCH monotonicity, sRGB/P3 gamut discipline, or dark-mode APCA polarity.

REJECT · 03Context-window bloat

60-Tool SaaS Mega-Servers

Mirrors every raw REST endpoint into tool schemas, burning thousands of tokens before the agent writes a single line of CSS.

THE ADJACENT BENCH / SUBSTITUTIONS BY STUDIO STACKKeep the worktable lean — swap, do not stack
Penpot MCP logo

Penpot MCP

Swap for #01 Figma · Open-source SVG/CSS stack
penpot.app ↗

Exposes native CSS Grid/Flex layout trees and open-standard design tokens directly from self-hosted or cloud Penpot files.

claude mcp add penpot -- npx -y @penpot/mcp-server@latest
Framer MCP logo

Framer MCP

Swap for #01 / #08 · Editorial & motion sites
framer.com ↗

Bridges CMS collections, responsive breakpoint stacks, and code-component overrides when publishing directly in Framer.

claude mcp add --transport sse framer https://mcp.unframer.co/sse
Webflow MCP logo

Webflow MCP

Swap for #01 / #05 · Visual DOM & CMS publishing
webflow.com ↗

Inspects Webflow Designer variables, class combo hierarchies, and structured CMS schemas without manual JSON exports.

claude mcp add webflow -- npx -y webflow-mcp-server@latest
Context7 MCP logo

Context7 MCP

Pair with #02 / #06 · Live post-cutoff specs
upstash.com ↗

Streams version-pinned Tailwind v4, CSS Anchor Positioning, View Transitions, and React 19 docs so models stop hallucinating deprecated config.

claude mcp add context7 -- npx -y @upstash/context7-mcp@latest
06 / Keep the canonical worktable at ten; swap instruments only when your authoring stack changesPenpot · Framer · Webflow · Context7

Fewer Tools, Sharper Instruments

You rarely need all ten of these running in the same session. On most days, my own working configuration comes down to three: Figma to read the structural intent, Chromologium (https://chromologium.com/mcp) to compute the chromatic and token math, and Chrome DevTools to verify what the browser actually drew.

The point of giving a model tools isn't to hand over the craft. Taste still belongs to the human in the chair — the person deciding what the software should feel like, what it owes the reader, and when a surface is quiet enough to let the work speak. What good MCP servers do is strip away the false confidence of machine guesswork. They let the calculator calculate, the browser render, and the designer actually design.