Magic MCP가 현재 21번째 MCP입니다. Magic MCP 서버(@21st-dev/magic)는 통합 21st MCP로 대체되었으며, 21st CLI를 통해 설치됨 — 21st.dev/mcp 설정됨. 이 패키지는 여전히 씬 호환성 프록시로 공개되어 기존 설정이 계속 작동하도록 합니다.

21번째 MCP 설치 (권장)

또는 수동으로 추가할 수도 있습니다 — 단순한 HTTP MCP 서버입니다:

21st.dev/mcp 에서 API 키를 받으세요.

구 매직 API 키가 초기화되었습니다. 이전 매직 콘솔에서 발행된 키는 더 이상 어디서도 작동하지 않습니다. 21st.dev/mcp 시 새 키를 생성하세요.

이 패키지가 지금 하는 일(v0.2.0+)

npx -y @21st-dev/magic@latest API_KEY="..."는 여전히 작동합니다: v0.2.0부터는 모든 MCP 메시지를 21번째 MCP 서버로 전달하는 작은 Stdio 프록시입니다. @21st-dev/magic를 참조하는 기존 mcp.json 항목들은 계속 작동하지만, 이제 인증된 계정에서 사용할 수 있는 도구를 사용할 수 있는 21번째 CLI와 동일한 서버에 통신합니다.

API 키는 위치 API_KEY="...", --API_KEY=..., /API_KEY:..., -API_KEY ..., TWENTY_FIRST_API_KEY / API_KEY_21ST 환경 변수 등 모든 과거 형태로 허용됩니다.

AI 접근

빌더 컴포넌트 접근은 호스팅된 21차 AI를 활성화하지 않습니다.

Magic MCP → 21st 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.

Install the 21st MCP (recommended)

npx @21st-dev/cli@latest init --client cursor   # or: claude | vscode | windsurf | codex

Or 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.

What this package does now (v0.2.0+)

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 tools available to the authenticated account.

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.

AI access

Builder component access does not enable hosted 21st AI. The server lists generate and iterate_generation only when AI access is enabled. Check get_usage.aiGenerationEnabled; this reports access, not the remaining AI credit balance. With AI off, use search and get_component, then adapt the code with your own coding agent. Existing drafts remain readable.

A cached or legacy generation call can return ai_subscription_required. Do not retry until AI is enabled. Refresh the client tool list or reconnect after enabling AI. The proxy forwards discovery to the server, so existing proxy versions receive this behavior without an npm update.

server.json mirrors the official dev.21st/mcp registry listing. The registry version is independent of this compatibility package version.

Old tool names → new tool names

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: