remixcn mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
RemixCN
shadcn components for Remix V3: accessible, dependency-free UI components, a shadcn-style registry, CLI and MCP server
RemixCN ports the shadcn/ui component catalog to Remix 3. You copy each component's source into your app and own it, as with shadcn/ui. The components need only remix, which your app already has: no React, Tailwind, or headless UI kit.
Site: https://janhesters.github.io/remixcn/ (not live yet)
Status
The workspace, the component inventory, the styling foundation, the registry build, the remixcn command line, and its MCP server are ready. registry/catalog.json lists the 67 planned entries and the batch each one lands in. registry/lib/ holds the theme stylesheet with its light and dark tokens, the shared style conventions, and the icons, and bun run style-reference shows them on a synthetic page. It also holds the shared behavior helpers for the overlay and selection components: focus, dismissal, modal, keyboard navigation, positioning, and hover intent. bun run build:registry turns registry.json into a registry in shadcn's format; so far it ships Attachment, Bubble, Button, Button Group, Carousel, Code Block, Marker, Message, Message Scroller, Resizable, Scroll Area, Slider, Dialog, Alert Dialog, Sheet, Drawer, Checkbox, Radio Group, Switch, Toggle, Toggle Group, Field, Input, Input Group, Input OTP, Label, Native Select, Textarea, Command, Questionnaire, Popover, Hover Card, Tooltip, Accordion, Collapsible, Tabs, Pagination, Sonner, Toast, Trace, Select, Calendar, Sidebar, the display and feedback components, the Typography and Date Picker recipes, the theme, the style conventions, the icons, the ARIA states helper, the civil dates helper, the dismissal, focus, modal, keyboard navigation, positioning, hover intent and mobile breakpoint helpers, and the license texts. Ported: Button, Button Group, Carousel, Code Block, Message Scroller, Resizable, Scroll Area and Slider, which bun run button-examples, bun run carousel-examples, bun run code-block-examples, bun run message-scroller-examples, bun run layout and bun run slider-examples show, Dialog, Alert Dialog and Sheet, which bun run dialog-examples shows, Drawer, which bun run drawer-examples shows, Checkbox, Radio Group, Switch, Toggle and Toggle Group, which bun run controls shows, Field, Input, Label, Native Select and Textarea, which bun run field-examples shows, Input Group and Input OTP, which bun run input-group-examples shows, Command, which bun run command-examples shows, Questionnaire, which bun run questionnaire-examples shows, Popover, Hover Card and Tooltip, which bun run overlays shows, Sidebar, which bun run sidebar-examples shows, Accordion, Collapsible, Tabs and Pagination, which bun run disclosure-examples shows, Sonner and Toast, which bun run toast-examples shows, Calendar and the Date Picker recipe, which bun run calendar-examples shows, Trace, which bun run trace-examples shows, Select, which bun run select-examples shows, Alert, Aspect Ratio, Avatar, Badge, Breadcrumb, Card, Direction, Empty, Item, Kbd, Progress, Separator, Skeleton, Spinner and Typography, which bun run display-examples shows, and Attachment, Bubble, Marker and Message, which bun run conversation-examples shows. docs/components/ describes each of them. The site's shell is ready too: the navigation, search, themes and the Button page as the first component page, which bun run docs serves and bun run build:site builds as static files for GitHub Pages. No other site page is ready yet, and nothing is published: the remixcn package isn't on npm, and the site and the registry aren't online.
Related MCP server: mnemo
Command line
remixcn sets up a Remix 3 app and copies items into it, with everything they depend on:
npx remixcn init
npx remixcn add button
npx remixcn search --query dialogIt installs no npm package, never replaces a file you changed without --overwrite, and undoes a whole install when one write fails. packages/cli/README.md documents every command, option, and exit code.
MCP server
remixcn mcp serves the registry to AI clients, such as Claude Code, Codex, Cursor, and VS Code, over MCP on stdio. It offers the seven tools of shadcn's MCP server, answered for Remix: list, search, and view items with their source, find examples, build the remixcn add command, and an audit checklist. The tools only read: they change no file, run no command, and open no port. packages/cli/README.md shows the config for each client.
Registry
Once the site is live, the registry is at https://janhesters.github.io/remixcn/r/registry.json, and each item at /remixcn/r/<name>.json. It follows the registry and registry-item schemas of shadcn 4.23.0. Items install only source files: no npm packages, since your app already has remix@3.0.0. Every item also installs RemixCN's license and the license texts of the projects it adapts.
remixcn add is the installer for Remix apps. shadcn's MCP server reads the registries map that remixcn init writes, so it lists, searches, and shows RemixCN items. shadcn's CLI can install them too. The tests check this setup with shadcn 4.23.0:
In
components.json, register"@remixcn": "https://janhesters.github.io/remixcn/r/{name}.json"and set the aliasesuito#remixcn/ui,libto#remixcn/libandcomponentsto#remixcn/components.In
package.json, map#remixcn/ui/*,#remixcn/lib/*and#remixcn/components/*underimportsto directories underapp/**/public/, so the browser can load them.For shadcn's
add, also set the fields its schema requires and RemixCN doesn't use:style,tailwindandaliases.utils.remixcn initdoesn't write them, since a Remix app needs no Tailwind.
Two of shadcn's install steps don't fit a Remix app:
Imports. shadcn keeps the
#remixcn/...tsimports. Thetsconfig.jsonof aremix newapp setsrewriteRelativeImportExtensions, and TypeScript then rejects these imports (TS2877). The app compiles once you remove that option.remixcn addrewrites them to relative paths instead.License header. shadcn drops the comment at the top of each TypeScript file, which holds RemixCN's license header. The license texts still arrive as files, since shadcn copies them unchanged.
Contributing
AGENTS.md describes the layout, the commands, and the contracts every change keeps.
bun install --frozen-lockfile
bun run checkbun run check runs every check that exists so far and says which are not built yet. CI runs the same checks for every pull request.
Credits
RemixCN adapts shadcn/ui and Base UI and builds on Remix. SOURCES.md lists what comes from where, and THIRD_PARTY_NOTICES.md holds their licenses.
License
MIT. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
List, search, and inspect Ply Angular + Tailwind copy-in components.
Provides tools to discover and list servers, agents, and skills in the AI Registry… — 想 7×24 常驻 → 萬星
Search shadcn registry items, read props and get exact install commands for React components.
Related MCP Servers
- AlicenseAqualityDmaintenanceExposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.3MIT
- AlicenseNot gradedqualityCmaintenanceServes local-first project memory over stdio, exposing tools to inspect project state, search and retrieve context, report memory, and create Git-aware checkpoints for coding agents.1Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to query accurate, up-to-date documentation for a React component library, including component lists, search, props, allowed values, defaults, and validated JSX usage examples over stdio.4MIT

si.sigit/cliofficial
FlicenseNot gradedqualityBmaintenanceServes sigit.si account, repository, issue, pull request, code-search, session, hook, and billing operations to AI agents over stdio, reusing the token stored by the CLI login and defaulting repository tools to the checkout the agent is pointed at. Tool lists can be trimmed with read-only mode or toolset selection, and a hosted HTTP endpoint offers the same tools.6-