What is the UISandbox MCP server?
UISandbox MCP is the server behind the UISandbox browser tool. It gives an AI coding agent five tools, load, set, export, verify and screenshot, to bring in a built web app, tune its colors, typography, spacing and shadows as variables, confirm the change renders correctly, then export updated styles as CSS, tokens or platform-specific code.
UISandbox is a browser-based tool that lets a built web app have its styling adjusted without a rebuild: it extracts CSS values as variables and exposes controls for color, typography, spacing, shadows and motion. The MCP server, published as uisandbox-mcp, exposes that same engine as tools for an AI coding agent.
An agent loads a build, changes a set of design variables, checks that the change renders as expected, then exports the result. The server replicates the browser tool's own engine rather than acting as a thin wrapper around it.
What it changes in your workflow
- The agent loads a built app from a zip, a local path or a GitHub or GitLab URL instead of asking a person to manually extract its styles.
- set adjusts design variables directly, so a color or spacing change is tested against the real rendered build rather than guessed from source code.
- verify runs a comparison between the original and modified build to check the change renders as intended before it ships.
- export turns the current variables into CSS, JSON, a patch list, or platform-specific code for the web, iOS or Android.
Setup at a glance
| UISandbox MCP server | |
|---|---|
| Run command | npx -y uisandbox-mcp |
| Transport | stdio, started by the client |
| Clients named | Claude, Cursor, Codex |
| Claude Code plugin | /plugin marketplace add Ideelab/uisandbox then /plugin install uisandbox@uisandbox |
Who it is for
Best for
- Teams that want to try a design change against a real built app before touching any source code.
- Design systems that need the same token set exported to CSS, Tailwind, shadcn, iOS Swift and Android Kotlin.
- Visual QA that compares an original and a modified build pixel by pixel before a change is approved.
Not for
- When the source is a live public website rather than an already built app sitting locally, the Dembrandt MCP server extracts colors, typography and spacing as design tokens directly.
- If the goal is picking from a curated visual style rather than editing an existing build's own values, the StyleKit MCP server supplies styles with tokens and a lint check.
- Choose a pure extraction tool when the only need is pulling colors, type and spacing from a public site into design tokens, the Extract Design System MCP server writes those tokens without touching a running build.
- Go with a Figma-first workflow when designs should be created or edited inside Figma Desktop itself, Conduit Design MCP operates Figma directly from plain prompts.
Use it with UiChemy
UISandbox retunes an already built web app's own styling. UiChemy's Composer instead builds and edits a WordPress page inside Elementor or Gutenberg from the start, so the two suit different stages of a project.
Connect UISandbox MCP Server for Live Style Editing to your AI client
npx -y uisandbox-mcpAdd the server to your client
Put the config above in your MCP client's settings, or run the equivalent add command.
Or install the Claude Code plugin
Run /plugin marketplace add Ideelab/uisandbox then /plugin install uisandbox@uisandbox for a bundled command plus the server.
Restart the client
Restart so the client starts the server over stdio through npx.
Load a build
Ask the agent to call load with a zip, local path or repository URL for the built app.
Adjust and verify
Call set to change a design variable, then verify to confirm the rendered result still matches expectations.
Client configuration
{
"mcpServers": {
"uisandbox": {
"command": "npx",
"args": ["-y", "uisandbox-mcp"]
}
}
}Endpoints and ports
uisandbox-mcpPublished npm package that the npx command runs.uisandbox@uisandboxInstalls a bundled command alongside the MCP server.What you can do with it
- No-rebuild stylingDesign values are extracted as variables from an already built app, so a style change does not require a rebuild step.
- Several export targetsThe same variables export as CSS, JSON, a patch list, web tokens for Tailwind or shadcn, iOS Swift constants, or Android Kotlin and colors.xml.
- Fidelity verificationThe verify tool compares the original and modified build so a design change can be checked before it ships.
- Headless screenshotsThe screenshot tool captures the current state in headless Chromium for a quick visual check.
- Flexible build sourcesThe load tool accepts a zip archive, a local path, or a GitHub or GitLab link for the built app.
- Bundled editor pluginAn agent-editor plugin install adds a dedicated command alongside the MCP server in one step.
Tools it exposes
load
Imports a built web app from a zip archive, a local path or a repository link.
set
Adjusts a design variable, such as a color, spacing or typography value, on the loaded build.
export
Generates the current variables as CSS, JSON, a patch list, or platform-specific code.
verify
Runs a comparison check between the original and modified build to confirm visual fidelity.
screenshot
Captures a render of the current build state in headless Chromium.
Frequently asked questions
What is the UISandbox MCP server?
It is the MCP server behind the UISandbox browser tool. It gives an AI coding agent tools to load a built web app, adjust its design variables, verify the visual result, and export the updated styles in several formats.
How do I install the UISandbox MCP server?
Add an entry to your MCP client's configuration that runs npx -y uisandbox-mcp as the command, then restart the client. Claude Code users can instead run the plugin marketplace add command for a bundled command plus the server.
What formats can it export to?
The export tool produces CSS, JSON, a patch list, web tokens for Tailwind or shadcn, iOS Swift constants and asset catalogs, and Android colors.xml plus Kotlin, all from the same set of design variables.
How does it check that a change is correct?
The verify tool runs a comparison between the original build and the modified one, checking that the rendered result matches what the design change was meant to produce before it is treated as final.
What kinds of builds can it load?
The load tool accepts a zip archive of a built web app, a local path, or a GitHub or GitLab repository link, so the same workflow applies whether the build is local or hosted.
Which AI coding agents does it work with?
The project names Claude, Cursor and Codex as supported clients. Any other MCP-compatible client that can run an npx command over stdio should connect to the server the same way.
Can it take a screenshot of the current state?
Yes. The screenshot tool renders the current build state in headless Chromium, which is useful for a quick visual check right after a design variable is changed or a new build is loaded.


