# matchcn

Discovers shadcn UI components across external registries by behavior and layout description rather than exact package names.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 17
- Author: francesco0242
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/francesco0242/matchcn
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/matchcn

## What it does

Component registries publishing a `registry.json` work smoothly with `npx shadcn add`, yet finding the right element usually stalls on naming mismatches. A prompt describing a three-tier pricing table misses components named after arbitrary adjectives. matchcn addresses this by indexing components across seven dimensions: category, domain, motion, visual density, interaction model, decorative purpose, and external data needs.

The server provides an agent with the `pick_component` tool. When given a plain-text brief, the tool applies deterministic matching against tagged properties and outputs the exact installation command alongside a dimension breakdown. When nothing fits closely, matchcn returns an explicit no-match response instead of forcing an irrelevant candidate.

Setting `resolve: "caller"` alongside known `hints` activates local ranking, cutting execution time to around 80 ms without outbound classifier calls.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add matchcn -- npx -y matchcn
```

### Codex

**Platform CLI**
```bash
codex mcp add matchcn -- npx -y matchcn
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "matchcn": {
            "command": "npx",
            "args": [
                "-y",
                "matchcn"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "matchcn": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "matchcn"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add matchcn npx -y matchcn
```

## When to use it
- find shadcn components by behavior rather than exact package name
- retrieve ready-to-run `npx shadcn add` commands for UI blocks
- select matching form or layout elements without browsing registry catalogs
- verify whether candidate components match requirements for animation and external data

## Example prompts
- Find a dense bento grid component for a landing page using matchcn and show the install command.
- Pick a login form with email and password inputs from shadcn registries using pick_component.
- Search for a three-tier pricing section component and check the property match breakdown.

## Similar
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74559
- [tldraw](https://affpapa.org/en/nevibecode/mcp/tldraw.md) — MCP server · ★ 51091
- [Figma-Context-MCP](https://affpapa.org/en/nevibecode/mcp/figma-context-mcp.md) — MCP server · ★ 16062
- [mcp-server-chart](https://affpapa.org/en/nevibecode/mcp/mcp-server-chart.md) — MCP server · ★ 4402
- [Dembrandt](https://affpapa.org/en/nevibecode/mcp/dembrandt.md) — MCP server · ★ 3821
- [RevoGrid DataGrid MCP Pro](https://affpapa.org/en/nevibecode/mcp/revogrid-datagrid-mcp-pro.md) — MCP server · ★ 3450

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md