How do I install the Shadcn MCP skill?

Run npx skillmds add majiayu000/shadcn-mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shadcn MCP safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shadcn MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shadcn MCP free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shadcn MCP?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shadcn MCP by majiayu000 — Agent Skill

Name: Shadcn MCP
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Shadcn Mcp

Overview

Install the shadcn MCP server and wire it into Codex so Codex can browse and install shadcn/ui components. This covers running the shadcn MCP init command, updating ~/.codex/config.toml, and restarting Codex.

Workflow

1. Choose the project context

Run the init command from any project directory where shadcn config makes sense (typically the frontend project where you use shadcn). Confirm the working directory if the user has multiple repos.

2. Run the shadcn MCP init command

Use the official command (requires network access):

npx shadcn@latest mcp init --client codex

If npx is not found in Codex environments (common with nvm), locate it and use the full path or ensure PATH includes it.

3. Add the MCP server to Codex config

Update ~/.codex/config.toml (create it if missing) with:

[mcp_servers.shadcn]
command = "npx"
args = ["shadcn@latest", "mcp"]

If you must use a full path to npx, update command accordingly.

4. Restart Codex and verify

Restart Codex. On startup, confirm the shadcn MCP server initializes successfully (no MCP startup errors).

Verification ideas:

Look for MCP startup logs in ~/.codex/log/.
Confirm Codex can list or fetch shadcn components (no MCP tool errors).

5. Troubleshoot common issues

If the MCP server fails to start, check that npx is available in the Codex environment.
If the config already contains a mcp_servers block, merge the shadcn entry without overwriting other servers.
If npx works in your shell but not in Codex, use the full path to npx in command.
If the MCP server errors on fetch, confirm the network is available and rerun npx shadcn@latest mcp.

---name: shadcn-mcpdescription: Install and configure the shadcn MCP server for Codex. Use when a user asks to enable shadcn/ui MCP tools, set up the shadcn MCP server in Codex, or troubleshoot shadcn MCP startup.--- # Shadcn Mcp ## Overview Install the shadcn MCP server and wire it into Codex so Codex can browse and install shadcn/ui components. This covers running the shadcn MCP init command, updating `~/.codex/config.toml`, and restarting Codex. ## Workflow ### 1. Choose the project context Run the init command from any project directory where shadcn config makes sense (typically the frontend project where you use shadcn). Confirm the working directory if the user has multiple repos. ### 2. Run the shadcn MCP init command Use the official command (requires network access): ```bash npx shadcn@latest mcp init --client codex ``` If `npx` is not found in Codex environments (common with nvm), locate it and use the full path or ensure PATH includes it. ### 3. Add the MCP server to Codex config Update `~/.codex/config.toml` (create it if missing) with: ```toml [mcp_servers.shadcn] command = "npx" args = ["shadcn@latest", "mcp"] ``` If you must use a full path to `npx`, update `command` accordingly. ### 4. Restart Codex and verify Restart Codex. On startup, confirm the `shadcn` MCP server initializes successfully (no MCP startup errors). Verification ideas: - Look for MCP startup logs in `~/.codex/log/`. - Confirm Codex can list or fetch shadcn components (no MCP tool errors). ### 5. Troubleshoot common issues - If the MCP server fails to start, check that `npx` is available in the Codex environment. - If the config already contains a `mcp_servers` block, merge the `shadcn` entry without overwriting other servers. - If `npx` works in your shell but not in Codex, use the full path to `npx` in `command`. - If the MCP server errors on fetch, confirm the network is available and rerun `npx shadcn@latest mcp`.

Frequently asked questions