21st.dev Magic (local)
Beta21st.dev's Magic server generates UI components from a prompt. It sends the prompt and the surrounding component code to 21st.dev's API and writes the result into the project.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- npx
- Platform
- macOS
- Publisher
- 21st.dev
How it works
Every agent request passes through Ferentin policy before it reaches 21st.dev Magic (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @21st-dev/magic.
Ferentin's endpoint agent finds 21st.dev Magic (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- 21st.dev Magic (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About 21st.dev Magic (local)
21st.dev's Magic server generates UI components from a prompt. It sends the prompt and the surrounding component code to 21st.dev's API and writes the result into the project.
Frequently asked about 21st.dev Magic (local)
- How do I connect 21st.dev Magic (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add 21st.dev Magic (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the 21st.dev Magic (local) integration generally available?
- The 21st.dev Magic (local) integration is currently beta on Ferentin.
Related integrations
3
AWS API (local)
AWS Labs' server runs AWS CLI commands for the agent with the AWS profile on the developer's Mac. Unless it runs in read-only mode, it can change anything that profile can.
AWS Documentation (local)
AWS Labs' server for searching the public AWS documentation. It needs no AWS credentials.
Azure (local)
Microsoft's Azure MCP server queries and operates Azure resources with the identity the developer's Azure CLI session already holds.