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
Server capabilities have not been inspected yet.
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
Multiple tools have unclear boundaries and overlapping purposes. The first three tools (component_builder, component_inspiration, component_refiner) all involve UI components with similar triggers like '/ui' or '/21' commands, making them easily confused. The logo_search tool is more distinct but still shares the UI component domain, creating potential misselection between generating new components and searching for logos.
The naming is mostly consistent with a clear prefix pattern ('21st_magic_component_' for three tools) and descriptive suffixes. However, the 'logo_search' tool breaks this pattern by using a different prefix style and simpler naming, which is a minor deviation from the otherwise predictable convention.
The tool count of 4 is well-scoped and appropriate for the server's purpose of UI component and logo management. Each tool appears to earn its place by covering distinct aspects like building, inspiration, refining, and logo search, without being overly sparse or bloated.
There are notable gaps in the tool surface for the UI component domain. While tools exist for building, refining, and getting inspiration for components, there is no tool for deleting, updating, or managing existing components (e.g., a 'component_deleter' or 'component_lister'). The logo_search tool provides good coverage for logos, but the component tools lack full lifecycle operations.