
It's like v0, but in your Cursor / Claude Code / Windsurf: search 10,000+ React/Tailwind components,
It's like v0, but in your Cursor / Claude Code / Windsurf: search 10,000+ React/Tailwind components, generate new UI with AI, and publish your own — right from your editor. Magic MCP is now the 21st MCP; this package keeps old configs working. Setup: 21st.dev/mcp
·
Magic MCP is now the 21st MCP. The Magic MCP server (
@21st-dev/magic) has been replaced by the unified 21st MCP, installed via the 21st CLI — setup at 21st.dev/mcp. This package remains published as a thin compatibility proxy so old configs keep working.
npx @21st-dev/cli@latest init --client cursor # or: claude | vscode | windsurf | codexOr add it manually — it is a plain HTTP MCP server:
{
"mcpServers": {
"21st": {
"url": "https://21st.dev/api/mcp",
"headers": { "x-api-key": "YOUR_21ST_API_KEY" }
}
}
}Get an API key at 21st.dev/mcp.
Old Magic API keys were reset. Keys issued by the old Magic console no longer work anywhere. Generate a fresh key at 21st.dev/mcp.
npx -y @21st-dev/magic@latest API_KEY="..." still works: since v0.2.0 it is a small stdio proxy that forwards every MCP message to the 21st MCP server. Existing mcp.json entries that reference @21st-dev/magic keep functioning — but they now speak to the same server as the 21st CLI, with the full current toolset.
The API key is accepted in all the historical forms: positional API_KEY="...", --API_KEY=..., /API_KEY:..., -API_KEY ..., or the TWENTY_FIRST_API_KEY / API_KEY_21ST environment variables.
The 21st MCP still accepts the legacy Magic tool names and translates them, so agents that remember the old names keep working. Prefer the new names:
| Legacy Magic tool | 21st MCP tool |
|---|---|
21st_magic_component_builder | generate |
21st_magic_component_inspiration | get_inspiration |
21st_magic_component_refiner | generate (new generation from the refinement prompt) |
logo_search | search_logo (one query per call) |
The current server exposes much more than the old four tools: catalog search across components/themes/templates, paid code retrieval, bookmarks, team libraries, UI generation with variants, profile management, and more. Connect and call tools/list to see the full set.
This repository is also packaged as an agent plugin (MCP server + a UI skill). You don't need to wait for any store — this repo IS a marketplace, add it directly:
# Claude Code
claude plugin marketplace add 21st-dev/magic-mcp # then: /plugin install 21st
# Grok Build
grok plugin marketplace add 21st-dev/magic-mcp && grok plugin install 21st --trust
# Codex CLI
codex plugin marketplace add 21st-dev/magic-mcp # then install "21st" from /pluginsSet your API key in the API_KEY_21ST variable (free key at 21st.dev/mcp).
Store listings:
API_KEY_21ST under Plugins → Configure. Get a key at 21st.dev/mcp.grok plugin install 21st --trust (from the official xAI marketplace), then export API_KEY_21ST..claude-plugin/ manifest: /plugin install it from any marketplace that lists this repo, or load locally with claude --plugin-dir . and export API_KEY_21ST.The plugin config expects the API key in the API_KEY_21ST variable in every client.
Why did my old Magic MCP stop working?
The Magic backend (magic.21st.dev) was superseded by the unified 21st MCP, and all old API keys were reset for security. Update to a fresh key from 21st.dev/mcp — your existing @21st-dev/magic config will then work again through this compatibility proxy, though we recommend switching to npx @21st-dev/cli@latest init.
Is /ui still a thing?
Use natural language: ask your agent to search 21st for components (search), or generate new UI (generate). The old /ui, /21 trigger phrases were a convention of the legacy tools' descriptions, not the protocol.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add 21st --transport http https://21st.dev/api/mcp{
"mcpServers": {
"21st": {
"url": "https://21st.dev/api/mcp",
"headers": {
"x-api-key": ""
}
}
}
}code --add-mcp '{"name":"21st","url":"https://21st.dev/api/mcp","headers":{"x-api-key":""}}'Runs as a hosted service. Your client connects over the network and nothing is installed locally.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/21st-dev-magic-mcp to learn what the "21st.dev Magic MCP" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx @21st-dev/cli@latest init --client cursor # or: claude | vscode | windsurf | codexThis server runs locally, so we can't read its tool list over the web yet.
A MCP for Claude Desktop / Claude Code / Windsurf / Cursor to build n8n workflows for you
A suite of specialized MCP servers that help you get the most out of AWS, wherever you use MCP.
MCP server for AI agents - search Meta, Google Ads, LinkedIn & TikTok ad libraries and analyze ad
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "21st-dev-magic-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
A MCP for Claude Desktop / Claude Code / Windsurf / Cursor to build n8n workflows for you
Developer Tools
A suite of specialized MCP servers that help you get the most out of AWS, wherever you use MCP.
Databases
MCP server for AI agents - search Meta, Google Ads, LinkedIn & TikTok ad libraries and analyze ad
Developer Tools
One email a week. New agents, MCP servers and skills, and what is actually getting traction.