What is MCP (Model Context Protocol)?
MCP (Model Context Protocol): MCP (Model Context Protocol) is an open standard that lets AI apps and coding agents call external tools and read data through small servers.
The Model Context Protocol is an open protocol, introduced by Anthropic in November 2024, for connecting AI applications to the tools and data they need. An MCP client lives inside the AI app (Claude Code, Claude Desktop, Cursor, VS Code with GitHub Copilot, Windsurf, Codex and many others). An MCP server is a small program that exposes capabilities to it. Because both sides speak one protocol, a server written once works in every client, the way a USB device works in any port.
How it works
- Tools are functions the model can call, such as
search_componentsorget_component. Each tool has a name, a description and a JSON Schema for its arguments, so the model knows when and how to use it. - Resources are read-only data the client can load into context, such as files or documents.
- Prompts are reusable templates a server offers to the user.
- Messages are JSON-RPC 2.0. A local server usually runs over stdio (the client starts it as a child process, often with
npx); a remote server uses Streamable HTTP.
Why it matters for UI libraries
A coding agent that writes UI from memory guesses at prop names and import paths, and its memory is months old. An MCP server for a component library replaces the guess with a lookup: the agent searches for the component it needs, reads the current props and an example, and installs it with the library's own command. The result is code that compiles on the first try and matches the library's design rules.
The shadcn CLI ships an MCP server that can browse and install from any shadcn registry, including MiniDev UI. Set it up for your client with npx shadcn@latest mcp init.
How MiniDev UI uses it
MiniDev UI also has its own server, hosted at https://ui.minidev.pro/mcp. It needs no install and no API key, and reads only public files: the registry at ui.minidev.pro/r and the public docs. Its tools are search_components (typo tolerant, by need: "date range picker"), list_components, get_component (props, install command, import line, example and full source), get_example, get_design_rules (tokens, shadows, radius, springs, materials) and get_install_instructions for Next.js, Vite and React Router.
# Claude Code
claude mcp add --transport http minidev-ui https://ui.minidev.pro/mcp
Setup for Cursor, VS Code, Windsurf and Codex is on Use MiniDev UI with AI agents. A typical agent run is search_components, then get_component, then npx shadcn@latest add @minidev/<name>, then a page written to get_design_rules.
An MCP server runs with your permissions. Before you add one, check what it reads and sends. Prefer servers that read public data only and keep tool calls visible so you can approve them.