21st.dev Magic AI Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your 21st.dev Magic API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 21st_magic_component_builderA | "Use this tool when the user requests a new UI component—e.g., mentions /ui, /21 /21st, or asks for a button, input, dialog, table, form, banner, card, or other React component. This tool ONLY returns the text snippet for that UI component. After calling this tool, you must edit or add files to integrate the snippet into the codebase." |
| logo_searchA | Search and return logos in specified format (JSX, TSX, SVG). Supports single and multiple logo searches with category filtering. Can return logos in different themes (light/dark) if available. When to use this tool:
Example queries:
Format options:
Each result includes:
|
| 21st_magic_component_inspirationA | "Use this tool when the user wants to see component, get inspiration, or /21st fetch data and previews from 21st.dev. This tool returns the JSON data of matching components without generating new code. This tool ONLY returns the text snippet for that UI component. After calling this tool, you must edit or add files to integrate the snippet into the codebase." |
| 21st_magic_component_refinerA | "Use this tool when the user requests to re-design/refine/improve current UI component with /ui or /21 commands, or when context is about improving, or refining UI for a React component or molecule (NOT for big pages). This tool improves UI of components and returns redesigned version of the component and instructions on how to implement it." |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The three 21st_magic_component tools have distinct purposes (build, inspire, refine), but the inspiration tool's description contains contradictory text about returning a text snippet, which could confuse agents into thinking it overlaps with the builder. Logo search is clearly separate, but the overlap between builder and inspiration creates some ambiguity.
Three tools follow a consistent 21st_magic_component_ prefix pattern, while logo_search deviates entirely, resulting in a mixed naming convention. All names are snake_case and readable, but the lack of a unified prefix makes the set feel somewhat inconsistent.
Four tools is a well-scoped size for a UI component agent, covering creation, refinement, inspiration, and logo lookup without unnecessary bloat. This fits comfortably within the typical 3-15 tool range and each tool has a clear role.
The tool surface covers the essential lifecycle for UI component work: create new components, refine existing ones, find inspiration, and search logos. Minor gaps exist, such as no explicit component analysis or listing tool, but agents can work around these without major failures.