UI Polish

com.uipolishPublished by uipolish.comOfficial publisherv1.0.1Updated Nov 6, 2026

React components and design rules your coding agent installs and follows.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Serves React UI components, design rules and color themes so a coding agent can install polished, state-complete UI into a project.

What you can do
  • Read design rules and checklists by topic (motion, states, typography, spacing, surfaces, anti-patterns)
  • List and fetch components, blocks and templates with code, guides, dependencies and npm packages
  • Generate a light and dark color theme from a single brand hue, with contrast-checked text colors
  • Return file paths so the agent writes each component and template file into the project
When to use it
Useful when a coding agent is building or refining a React interface and you want consistent, opinionated components and design rules rather than ad-hoc styling. It fits projects that want ready-made states, motion and accessibility details, including Tailwind CSS v4 setups.
Requirements
A remote MCP endpoint at uipolish.com added over streamable HTTP; no authentication, environment variables or headers are declared. The target project needs React, and interactive components need the @base-ui/react package; Tailwind v4 projects need the bridge set up once.
Before you install
The server writes files into your project, so review what it adds and where. Some listed components, blocks and templates are marked pro and require a paid UI Polish Pro plan; the free tier is MIT-licensed. It also asks the agent to map its tokens onto existing project variables rather than adding a second palette.

Installation

In SourceWeft

  1. Open UI Polish in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.uipolish%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ui-polish": {
      "type": "http",
      "url": "https://uipolish.com/mcp"
    }
  }
}

README

UI Polish

Polished UI for AI products: React components where every state, transition and edge case is already worked out, and the design rules behind them, written so coding agents can follow them. Docs and live demos at uipolish.com.

This repository is the free tier, under the MIT license: 45 components, 10 agent-kit pieces and blocks, the tokens and theme generator, the design rules and the agent skill.

The opinions

Every component makes the same calls, and the rules ask the same of the UI your agent writes around them. Three of them:

  • Busy waits 300ms before it shows. A fast answer never flashes a spinner. Once a spinner appears, it stays at least 400ms so it can be read.
  • Every async action has four states. Idle, busy, done and failed, each designed, with the failure saying what to do next.
  • Nothing shifts. Labels that change hold their width, numbers use tabular figures, and content that loads in has its space reserved.

All ten are in foundation/opinions.md.

Three ways in

1. The MCP server. Connect it once, then ask your agent for a component by name ("add a date picker"). It writes the files into your project and follows the rules for the UI it writes itself.

bash
claude mcp add --transport http uipolish https://uipolish.com/mcp

Setup for Cursor, VS Code, Codex and other clients is at uipolish.com/docs.

2. The shadcn CLI. Every item has a registry file in r/. Point the CLI at one, from uipolish.com or from this repository's raw files:

bash
npx shadcn@latest add https://uipolish.com/r/date-picker.json
bash
npx shadcn@latest add https://raw.githubusercontent.com/cortez/uipolish/main/r/date-picker.json

Any item works the same way: https://uipolish.com/r/<name>.json or https://raw.githubusercontent.com/cortez/uipolish/main/r/<name>.json.

A component brings the components it uses and installs the tokens once. r/theme.json maps the tokens onto an existing shadcn/ui theme instead.

3. The rules file. skills/ui-polish/ is the design rules as an agent skill: copy the folder into your agent's skills directory (.claude/skills/ for Claude Code), or point your agent at SKILL.md from AGENTS.md. The same rules, one file per topic, are in foundation/rules/.

You can also copy a folder from registry/ by hand, with foundation/tokens.css once. The interactive components need @base-ui/react.

What's here

  • registry/<name>/: one component: the React component, its CSS module (it reads --ui-* tokens only), guide.md for agents and meta.json. animated-size, field, icons, listbox, text and text-morph are building blocks the others import.
  • foundation/: the opinions, the rules, tokens.css, the Tailwind v4 bridge, the shadcn mapping and the checklist.
  • theme/theme.ts: one hue in, a whole light and dark --ui-* palette out, with every text color solved for contrast. Paste its CSS after tokens.css.
  • skills/ui-polish/: the agent skill, built from foundation/.
  • r/: the shadcn registry, built from registry/ and foundation/.

UI Polish Pro adds whole product screens, templates and more agent-kit pieces: uipolish.com/pricing.

Components

  • Accordion: Disclosure sections that open on a grid-row transition, one or several at a time. An item named in the URL hash is already open on first paint.
  • Alert: Inline banner for info, success, warning and error. It reserves its space up front or opens on a press, so a late status never pushes the page.
  • Avatar: Photo with initials on an opaque quiet fill behind it, or a head and shoulders with no name. A quick photo never flashes initials, a broken one never shows its broken mark, and groups overlap with a +N that says how many.
  • Badge: A static label for a status or a count, exactly as tall as the line it sits in. Counts are round for one digit and set in equal-width figures.
  • Breadcrumbs: Trail of links to the current page. A long middle folds into a … that opens in place, long labels fade instead of wrapping, and any router’s link fits.
  • Button: Pill button that presses instantly and springs back. The busy state keeps its width, and the label morphs when its text changes.
  • Checkbox: Base UI checkbox whose tick draws on and off. The mixed-state dash morphs into the tick, and the box aligns to the first line of its label.
  • Chip: Filter chips that stay pressed, and removable chips with their own named remove button. A plus swings into a check without changing the width, and removed chips fade before the rest slide into place.
  • Code input: One-time code boxes that fill from a paste or platform autofill and step back on Backspace. The active box shows a dark edge and a caret, invalid shows in the edges; an optional status folds the boxes into a centered, edgeless Verifying pill that turns to Verified, or opens back up on a wrong code.
  • Combobox: Type-to-filter autocomplete for local or async results. Each match marks the typed text, and stale results stay in place while new ones load.
  • Command palette: ⌘K palette with fuzzy matching, recents and grouped results. Async sources never flash a loading state, and the height follows the results.
  • Copy field: Read-only value with a Copy button whose icon turns into a check and says “Copied” to screen readers. A secret masks as a fixed row of dots that gives away nothing about its length.
  • Data table: Keyboard-first grid for real data: one tab stop, arrow keys between cells, a stable sort whose arrow flips its head, columns resized by pointer or keys, range selection, and thousands of rows virtualized without a dependency.
  • Date picker: Date field that opens a calendar dialog with full grid keyboard support. Months slide a short way in the direction you moved, crossfading inside a soft-edged panel, and ranges are optional.
  • Dialog: Modal that grows out of its trigger and eases to fit its content as steps change. It locks scroll without a shift and asks before discarding edits.
  • Drawer: Modal panel that slides in from the end edge, and on phones rises as a sheet you drag down to dismiss, at the speed of your flick. The body scrolls between a header and footer that stay put.
  • Dropdown menu: Menu button with checkbox, radio and submenu items. Submenus forgive a diagonal pointer path, and pointer and keyboard share one highlight.
  • Empty state: The message for an empty list or view: a clean isometric line drawing with crisp corners (a stack, a box, a folder, a tray, a magnifier, a calendar or an unplugged cord), drawn once as it comes into view, with a title, one sentence and one action.
  • File upload: Drop zone with a fixed-height file list. Each row fills with its upload progress, and the list scrolls inside its height, so the page never moves.
  • Inline edit: Text that becomes an input where it stands, in the same font and the same place, so not a letter moves. Enter saves, Escape restores, and an error keeps you editing.
  • Kbd: A key or a shortcut as the reader’s keyboard labels it: ⌘K on Apple, Ctrl K elsewhere. Decided before the first paint, so the server and the browser agree and nothing moves.
  • List: Rows of peers, static, links or buttons, each row one tab stop with nothing nested inside it. Secondary actions show on hover or focus without moving anything, and every row keeps its height in every state.
  • Nav rail: A compact app rail of icon items. One tooltip glides from item to item, easing to each label’s width with the shortcut beside it, and a raised capsule glides to the current page.
  • Number input: Spinbutton whose − and + buttons speed up while held. A typed value outside min or max is pulled into range, with a note that says so.
  • Pagination: Page numbers in a fixed number of slots, so the control never changes width as you page. Numbers slide under one moving pill, and Next stays focusable at the end.
  • Phone input: Phone field with a country picker. The number groups as you type without moving the caret, a pasted +44 number picks its country, and the form gets E.164.
  • Popover: Click-triggered panel anchored to its trigger. It moves focus into forms, leaves it on the trigger for explanations, and returns it on close.
  • Progress: Linear progress whose fill moves on a spring. The indeterminate state sweeps a band of light through the track, and a segmented variant shows named steps.
  • Prompt input: Chat composer that grows with its text and sends on Enter, never mid-IME. Send turns into Stop while a reply streams, and dropped files become chips.
  • Radio group: Base UI radios in a fieldset, as a list or as cards. The mark opens from its center, arrow keys choose, and the whole group takes one tab stop.
  • Response actions: The row under an assistant reply: copy, thumbs up and down, and retry. A thumbs down can open a “What went wrong?” field in place.
  • Scroll area: Scroll container whose edges fade with a mask only where more content remains. It works on any background and scrolls by keyboard.
  • Search field: Search input whose clear button fades in over room it already holds, so the text never moves. Escape clears, then leaves, and the magnifier breathes while results load.
  • Segmented control: Base UI radio group with the Tabs' look: a clear hairline track and one flat pill that glides to the checked option. Arrow keys and form values come with the group.
  • Select: Select-only combobox whose trigger fits the chosen label and morphs to the next one. Touch screens get the native picker instead.
  • Sidebar: The app sidebar for an AI product: a workspace switcher, items with counts and shortcuts, folding sections, a recent chats list with rename, pin and delete, and an account menu. Collapses to an icon rail with one gliding tooltip, and becomes a drawer on phones.
  • Skeleton: Placeholders shaped like the content on its way, with text lines exactly as tall as the text, so the swap moves nothing. One element per bone; one soft diagonal sheen crosses every skeleton on the page together, and nothing shows for loads under 300ms.
  • Slider: A label row with a steady-width value over a sunken track, an accent range and a raised capsule thumb that glides to place. Base UI's slider underneath handles pointer, keyboard and touch.
  • Stat: A figure with its label and a change stated by both an arrow and words. The hint always takes two lines, so tiles in a row stay level.
  • Switch: Base UI switch with role="switch": the segmented control in miniature, a sunken track with a raised pill that glides across. Two sizes on the control scale and a busy state for saves.
  • Tabs: Tabs built on Base UI, with a pill that stretches from one tab to the next. Optional URL sync supports back and forward, and panels crossfade in place.
  • Text field: Labeled input that validates when you leave it and clears the error as soon as the value is fixed. The error takes the hint’s line, so nothing shifts.
  • Theme toggle: Icon capsule that switches light and dark: one drawing where the sun's disc grows into a crescent as a second circle slides over it. Stores the choice, follows the system until there is one, and paints the right theme before the first frame.
  • Toast: Imperative toasts in a collapsed stack that fans out on hover. Timers pause while you read, and a flick swipes a toast away.
  • Tooltip: Short hint that opens after a pause, then instantly as you move between triggers. Keyboard focus opens it at once.

Agent kit and blocks

  • Agent settings: A whole settings screen for an AI agent, built from the kit: model, MCP connections, what it may do without asking, a daily spending limit and memory. Every change saves in its row, and a sticky section nav follows you down the page.
  • Authorize: The consent screen an MCP server shows when an agent asks to connect: who's asking, what it will be able to do, and where you go back to. Risky permissions start off.
  • Code block: Code block for AI apps that streams in without flashing or jumping. Copy, line wrap and calm token-colored highlighting are built in, with no highlighter library.
  • Connections: The agent app's list of MCP servers: one quiet row each, a switch, and a status line that says what's wrong and the one thing that fixes it. Adds a server by URL and hands sign-in to the browser.
  • Diff view: Unified diff with the changed part of each line marked and unchanged stretches folded. In streaming mode, new lines fade in as they arrive.
  • Markdown: Renders a model's markdown reply while it streams: no flash of raw asterisks, backticks or half-typed tables, code fences open as live code blocks, and HTML in the reply shows as text.
  • Message thread: Chat transcript that fades in only the newly streamed words. It stays pinned to the bottom until you scroll up and announces each reply once it ends.
  • Model picker: Compact trigger that resizes to fit the current model’s name. It opens a list of models with one-line descriptions and a drawn check on the selection.
  • Sign in: A passwordless sign-in and sign-up screen: work email, then a one-time code with a resend countdown, plus optional OAuth providers and SSO by work domain. Wrong, expired and rate-limited codes, blocked domains and failed providers each say what to do next.
  • Usage meter: How much of an agent’s context window or spending budget is used, as a ring and a percentage in the composer toolbar. Opens to a breakdown, warns before the limit and offers to compact.

License

MIT. See LICENSE.

Source: README.md at commit 9b475c3

Tools

4

get_rules

Foundation rules: concrete values for motion, states, typography, spacing, surfaces, focus and anti-patterns. Pass a topic for one file; omit it for the token roles, the finished? checklist and the list of topics.

Parameterstopic

list_components

Every UI Polish template, block and component with a one-line summary and version. Templates are whole working apps (a chat app, an agent console, an agent workspace for coding); blocks are whole screens (sign-in, billing, team members, an approvals inbox, an agent task). Those marked pro need a UI Polish Pro license key.

Takes no parameters.

get_component

The code and guide for one component, block or template: when and when not to use it, every state, motion specs, accessibility notes, before/after. Includes the components it depends on and the npm packages to install. A template's own files come with the project path to write each one at (app/(app)/chat/page.tsx). Pro blocks and templates need a license key on the connection; without one they return a summary and how to get one.

Parametersnamerequiredstacktailwind

get_theme

A color theme from one hue: the --ui-* accent, the text on it and in it, optionally tinted grays and accent primary buttons, light and dark, with every text color solved for 4.5:1 contrast. Returns CSS to paste after tokens.css. Use it when the project has a brand color.

Parametershuerequiredtintbrand

Version history

1
  1. v1.0.1LatestNov 6, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts