# Arc UI [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/kuratlielia/arc-library  
**GitHub Stars:** 758  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/arc-ui

## Description
React components and blocks with motion. Search docs, props and shadcn install commands.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "arc-ui": {
    "command": "npx",
    "args": ["-y","shadcn@latest"]
  }
}
```

## Documentation

## What Arc UI MCP server does

The Arc UI MCP server gives an AI agent access to reference information for Arc UI, a React component and block library. Its documented purpose is to search Arc documentation, look up component props, and provide shadcn installation commands. This makes it relevant when a developer wants an agent to identify an Arc item, inspect its available properties, or determine how to add it to an application.

Arc’s repository contains 110 components and 22 blocks in the free, open-source collection. The library uses plain source files that developers own after installation. Its components use CSS modules and shared design tokens, while motion behavior is provided by the `motion` package. The library supports Next.js and Vite projects and does not require Tailwind.

## How it works

The Arc UI MCP server is presented as an AI and MCP feature for the Arc documentation site. Based on the supplied description, an agent can search the documentation rather than relying only on a local copy of the repository. Searches can cover component documentation and props, while installation requests can return the relevant shadcn CLI command.

The returned installation guidance belongs to Arc’s shadcn registry workflow. Arc documents both the `@uiarc` registry namespace and direct registry URLs. A component or block may bring along local dependencies through the CLI. The documentation also describes a separate `@uiarc/arc-foundation` installation for shared design tokens, which applications import from their root entry point.

## Tools and capabilities

The Arc UI MCP server supports these documented use cases:

- Search Arc UI documentation.
- Find component prop information.
- Retrieve shadcn installation commands.
- Identify documentation for Arc components and blocks.

The source material does not provide formal tool names, input schemas, output schemas, transport details, or a server startup command. Those implementation details should be verified in the repository or the Arc AI and MCP documentation before configuring an agent.

## Limitations and notes

The Arc UI MCP server should be treated as a documentation and installation-reference tool, not as a runtime component library. The supplied material does not state that it edits files, installs packages directly, previews components, or invokes the shadcn CLI on the developer’s behalf.

Arc projects have specific documented requirements: React 19 with TypeScript, an ES2023-or-newer library target, and the `@/*` import alias. Animation-dependent items use `motion`; some also use `lucide-react` or Radix UI primitives. These are requirements of the components being installed, not stated requirements for the MCP server itself.

The README identifies an MIT license for the repository. It does not name supported MCP clients, environment variables, or client-specific configuration. The repository includes free components and blocks, while items marked Pro belong to Arc Pro and are not part of the free repository.

_Full upstream README: https://allmcps.com/mcp/arc-ui/readme_