AceternityUI_MCP_Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set logging level (debug, info, warn, error) | info |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_componentA | Get detailed information about a specific Aceternity UI component by its slug |
| list_componentsA | List all available Aceternity UI components, optionally filtered by category |
| search_componentsA | Search for Aceternity UI components by name, description, or tags |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| component_usage | Get guidance on how to use a specific Aceternity UI component |
| animation_guide | Get recommendations for animation and effect components |
| background_selector | Get help choosing the right background component for your needs |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Aceternity UI Components List | List of all available Aceternity UI components |
| Component Categories | Categories of Aceternity UI components |
TDQS
Scored across 3 tools
The three tools have distinct purposes: list for browsing, search for querying, and get for retrieving a specific item. However, list with category filtering and search by text could occasionally overlap if users search by category name, but descriptions clarify the intended use.
All tool names follow the consistent verb_noun pattern: get_component, list_components, search_components. The pattern is uniform and predictable.
Three tools is minimal but appropriate for a read-only component browsing server. It covers the core operations without bloat, though one additional tool (e.g., get_categories) might round it out slightly.
For its purpose of browsing a UI component library, the set provides list, search, and detail retrieval—covering the essential workflows. A minor gap is the lack of an explicit category listing endpoint, but list_components with category filtering mitigates this.