Does 21st.dev have an MCP server?

Yes Official

21st.dev maintains an official MCP server.

Verified 2026-09-29 against vendor docs
Access
Remote server
Endpoint
https://21st.dev/api/mcp
Maintainer
21st Labs
License
ISC
Language
TypeScript
Stars
5.9k
Last commit
20d ago
What it does
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
— how 21st-dev/magic-mcp describes itself

Project site: 21st.dev

The receipts
Vendor-hosted https://21st.dev/api/mcp

A remote server run by 21st.dev itself — nothing to install. Documented at 21st.dev.

Official repository 21st-dev/magic-mcp

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

★ 5.9k pushed 2026-09-09 ISC Active
Connect it

Hosted by the vendor — no install, connect over HTTP with OAuth or a token.

Add it from the terminal, then restart your session:

terminal
claude mcp add --transport http 21stdev https://21st.dev/api/mcp

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does 21st.dev have an official MCP server?

Yes. 21st.dev maintains an official MCP server, hosted at https://21st.dev/api/mcp. The source lives at 21st-dev/magic-mcp on GitHub.

How do I connect 21st.dev to Claude?

Add https://21st.dev/api/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http 21st-dev https://21st.dev/api/mcp" in Claude Code.

Do I need to install anything to use the 21st.dev MCP server?

No. It is a remote server hosted by 21st.dev, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.

How is this verdict verified?

Published to the MCP Registry under 21st.dev's verified namespace dev.21st; 21st.dev/mcp documents the API-key hosted endpoint 21st.dev/api/mcp (answers MCP initialize with 401), and the 21st-dev/magic-mcp repo holds the legacy Magic MCP package that it replaced. GitHub metadata is refreshed every six hours.

How we know

Published to the MCP Registry under 21st.dev's verified namespace dev.21st; 21st.dev/mcp documents the API-key hosted endpoint 21st.dev/api/mcp (answers MCP initialize with 401), and the 21st-dev/magic-mcp repo holds the legacy Magic MCP package that it replaced.

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Developer Tools

See all Developer Tools servers →