Finance
21st-ui - Claude MCP Skill
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
SEO Guide: Enhance your AI agent with the 21st-ui tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to find, install, and generate ui with 21st.dev. use when the user asks for a ui component (pricing tab... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# 21st.dev UI Skill 21st.dev is a marketplace of 10,000+ production-ready React/Tailwind (shadcn-compatible) components, plus AI UI generation. This skill drives the 21st MCP server. ## When to reach for it - The user asks to add/build a UI element: "add a pricing section", "I need a nice navbar", "make a testimonials block". - The user wants options or inspiration before committing to a design. - The user needs a company logo in JSX/TSX (`search_logo`). - The user wants brand-new UI generated from a description (`generate`). ## Workflow: install an existing component (default path) Prefer real catalog components over writing UI from scratch — they ship with dependencies, demos, and responsive/dark-mode support. 1. `search` with a short natural query (e.g. "pricing table", "animated hero"). Results include names, descriptions, previews, and install ids. 2. Pick the best match for the user's stack and style; show the user 1–3 top candidates if the choice isn't obvious. 3. `get_component` to fetch the full code and metadata for the chosen item. 4. Install into the project the way the result instructs (shadcn-style registry add or by writing the returned files), then wire it into the page and adapt tokens/props to the project's design system. Notes: - Free tier allows catalog search and 2 component installs per day; paid components return code only after unlock. - Match the project's existing conventions (Tailwind config, cn helper, component folder layout) when integrating. ## Workflow: generate new UI When nothing in the catalog fits or the user explicitly wants custom UI: 1. Check `get_usage.aiGenerationEnabled` and the current `tools/list`. Paid component access alone does not enable hosted AI. Missing or unknown status is not permission to generate. 2. With AI off, use `search` and `get_component`, then implement or adapt the UI with your own coding agent. Do not call generation tools, legacy builder/refiner aliases, or the CLI as a workaround. 3. When AI is enabled and `generate` is listed, call it with the purpose, layout, content, style, and stack constraints. It consumes AI credits and returns a preview URL; open that URL to view the generation. 4. For existing sketch drafts, use `get_generation` and `get_take` to read their code. These reads remain available with AI off. If a cached call returns `ai_subscription_required`, stop generation attempts. After enabling AI, refresh the tool list or reconnect before trying again. The entitlement flag does not report the remaining credit balance. ## Logos `search_logo` returns brand logos as ready-to-paste JSX/TSX — one brand per call. ## Setup and auth The server is HTTP MCP at `https://21st.dev/api/mcp`, authenticated with the `x-api-key` header. Keys are free and instant at https://21st.dev/mcp. If a call fails with an auth error, tell the user to grab a key there and set it in the plugin configuration (variable `API_KEY_21ST`). Legacy Magic tool names (`21st_magic_component_builder`, `logo_search`, ...) are still accepted server-side, but prefer the current names: `search`, `get_component`, `generate`, `get_inspiration`, `search_logo`.
Signals
Information
- Repository
- 21st-dev/magic-mcp
- Author
- 21st-dev
- Last Sync
- 11/2/2026
- Repo Updated
- 11/2/2026
- Created
- 8/31/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cursorrules
CrewAI Development Rules
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
Related Guides
Bear Notes Claude Skill: Your AI-Powered Note-Taking Assistant
Learn how to use the bear-notes Claude skill. Complete guide with installation instructions and examples.
Mastering tmux with Claude: A Complete Guide to the tmux Claude Skill
Learn how to use the tmux Claude skill. Complete guide with installation instructions and examples.
OpenAI Whisper API Claude Skill: Complete Guide to AI-Powered Audio Transcription
Learn how to use the openai-whisper-api Claude skill. Complete guide with installation instructions and examples.