Server data from the Official MCP Registry
React components and design rules your coding agent installs and follows.
About
React components and design rules your coding agent installs and follows.
Remote endpoints: streamable-http: https://uipolish.com/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
4 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"com-uipolish-mcp": {
"url": "https://uipolish.com/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
UI Polish
Polished UI for AI products. React components and whole screens for chat, agents and everything around them, where every state, transition and edge case is worked out, and the design rules behind them, made for coding agents. All of it is free and MIT-licensed: the components, the AI components that show a model thinking, acting and asking, whole product screens (blocks) and whole apps built from them (templates).
Docs · Components · Design rules · Theme builder
Start
Pick one. None needs an account or a key.
Let your agent do it. Connect the MCP server, then ask for components by name ("add a date picker"):
claude mcp add --transport http uipolish https://uipolish.com/mcp
Cursor, Codex, VS Code, Gemini CLI and others: uipolish.com/docs.
Use the shadcn CLI. Any component by name, with what it depends on:
npx shadcn@latest add https://uipolish.com/r/dialog.json
Just the rules. The design rules as a skill your agent follows for the UI it writes itself (skills/ui-polish):
mkdir -p .claude/skills/ui-polish && curl -fsSL https://uipolish.com/skill.md -o .claude/skills/ui-polish/SKILL.md
Opinions
Ten decisions every component shares. Each is a token or a rule, so changing one value changes every component that uses it.
- Leave fast, arrive slower.
- Springs only where something moves.
- Busy waits 300ms before it shows.
- Every async action has four states.
- Edges come from the text color.
- Focus is for keyboards.
- Nothing shifts.
- One shape per job.
- Native and accessible first.
- Reduced motion keeps the meaning.
The values behind each: foundation/opinions.md.
What's in it
Foundation
foundation/rules/: concrete rules for motion, states, typography, spacing, surfaces, focus and the anti-patterns that pass code review. Each gives concrete values: durations, easings, shadow recipes, tracking.foundation/tokens.css: the--ui-*roles every component reads (space, radius, control heights, durations, easings including a critically damped spring, color, focus ring, three elevations). Map them onto the variables your project already has; UI Polish doesn't bring a theme.foundation/checklist.md: yes/no checks to run before calling UI done.
Components
One folder per component in registry/: the React component, its CSS module
(tokens only), and a guide covering when to use it, when not to, every state,
motion specs, accessibility and before/after code.
Components (45): Accordion, Alert, Avatar, Badge, Breadcrumbs, Button, Checkbox, Chip, Code input, Combobox, Command palette, Copy field, Data table, Date picker, Dialog, Drawer, Dropdown menu, Empty state, File upload, Inline edit, Kbd, List, Nav rail, Number input, Pagination, Phone input, Popover, Progress, Prompt input, Radio group, Response actions, Scroll area, Search field, Segmented control, Select, Sidebar, Skeleton, Slider, Stat, Switch, Tabs, Text field, Theme toggle, Toast and Tooltip.
Agent kit: components for AI products, grouped in the docs by
"kit": "agent" in meta.json: Agent settings, Authorize, Background run,
Batch progress, Code block, Connections, Diff stat, Diff view, File changes,
Markdown, Merge status, Message thread, Model picker, Pipeline, Plan
approval, Reasoning, Research progress, Sources, Tool approval, Tool steps,
Turn summary, Usage meter and Voice input.
The interactive components run on Base UI
(@base-ui/react) for focus, keyboard, ARIA, positioning and dismissal; the
look, motion and states are UI Polish's own CSS modules. A component lists the
packages it imports in meta.json (packages), and get_component, the REST
API and the shadcn registry item all tell the project to install them.
Templates: Chat app,
a working AI chat app for the Next.js App Router:
emailed-code sign-in, the Sidebar with workspaces and chat history, chats
streaming through a Route Handler from Claude, OpenAI or any
OpenAI-compatible API (set by AI_PROVIDER, AI_API_KEY and AI_MODEL; a
mock until one is set), and settings built from Agent settings, Billing
and Team members. Agent console, a
working console for operating AI agents: live runs and their traces (Run
history), an approvals inbox that pauses a run until someone decides,
Knowledge base, per-agent Agent settings, usage and workspace Settings, with
a mock runner behind one AgentRunner interface until yours is in. Agent
workspace, a three-pane app for
coding with agents: sessions as tabs over a conversation whose tool calls
fold to one line (Turn summary), file chips with diff stats, the pull
request's Merge status, its files (File changes), checks and diff, a run
panel, and a team sidebar with presence, with a scripted coding agent behind
one CodingAgent interface until a model or yours is in. A template's
folder in registry/ mirrors a Next.js project: "type": "template" in
meta.json lists each file (files) by the path it installs at, and its
dependencies are the components and blocks it uses. get_component and
/r/<name>.json serve those files with their project paths (shadcn
target), next to the components at components/ui/<name>/.
Building blocks, written alongside the components that need them: Animated size, Field, Icons, Listbox, Text, Text morph.
list_components (or GET /api/components) is the live list.
MCP tools
| Tool | What it does |
|---|---|
get_rules(topic?) | One rules file, or the tokens, checklist and topic list |
list_components() | Names, summaries, versions, and which are in the agent kit |
get_component(name, stack, tailwind) | Code and guide, including the components it depends on and the packages to install |
get_theme(hue, tint, brand) | A one-color theme: accent, text on it, tinted grays, light and dark, contrast-checked (also GET /api/theme, and /docs/theme by hand) |
Tailwind CSS
In a Tailwind CSS v4 project, agents pass tailwind: true to
get_component: the CSS modules come inside Tailwind's components layer,
so utility classes override them. foundation/tailwind.css names the
--ui-* roles as theme values (bg-ui-surface, text-ui-muted), and
foundation/tailwind.md is the setup guide, served as get_rules("tailwind")
and at /docs/tailwind.
shadcn CLI
Every component is also a shadcn registry item: npx shadcn add https://uipolish.com/r/dialog.json, or add the @uipolish registry to
components.json and run npx shadcn add @uipolish/authorize. /r/registry.json lists every item;
/r/theme.json maps the roles onto a shadcn theme (foundation/shadcn.css).
Setup: foundation/shadcn.md, served at /docs/shadcn.
For agents without MCP
GET /api/components,/api/components/{name},/api/rules,/api/rules/{topic}: the same content as JSON, with no key. Described by/openapi.json; errors are JSON with a code, a message and a hint.- Every page as Markdown: send
Accept: text/markdown, add.mdto the path, or read/md/<path>. Docs pages also have a Copy page button. /llms.txtand/llms-full.txt: what UI Polish is, when to use it, and every guide in one file.
Develop
npm install
npm run dev # site, previews at /preview/<name>, MCP at /mcp
npm run build
npm test # needs the build: starts it, or set BASE_URL
# the layout check runs when Playwright is installed
Try the MCP endpoint:
curl -s localhost:3000/mcp -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_components","arguments":{}}}'
Repo layout
foundation/ opinions, rules, tokens, checklist, the skill template
registry/ one folder per component: .tsx, .module.css, guide.md, meta.json
skills/ the rules as an agent skill, built from foundation/ (npm run skill)
src/app/ site, previews, MCP route, REST API, Markdown twins
src/lib/ content loader, MCP tools, API, SEO and llms.txt
src/proxy.ts serves Markdown to requests that ask for it
tests/ node:test suites against a production build
Contributing
Issues and pull requests are welcome. A change to a component touches its
.tsx, .module.css, guide.md and a version bump in meta.json; the
guide is part of the component, since it's what agents read. After changing
anything in foundation/, run npm run skill. Run npm run typecheck,
npm run lint and npm test before opening a PR. AGENTS.md has
the conventions, for people and coding agents alike.
License
MIT. See LICENSE. The site's fonts (DM Sans and DM Mono) are under the SIL Open Font License.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
