aceternityui

The Aceternity UI MCP server provides a programmable interface to search, inspect, and install Aceternity UI components through the Model Context Protocol. It exposes tools to search components by name, description, or tags, retrieve detailed component information, obtain installation commands and setup guidance, and list available categories and components. This makes it easy for AI assistants, chatbots, and other applications to discover UI components and present precise installation steps to users.

To use it, connect to the MCP server via the standard MCP transport (stdio for many clients) and call the available tools such as search_components, get_component_info, get_installation_info, list_categories, and get_all_components. Each tool returns structured data that can be integrated into your UI or assistant responses, enabling seamless discovery and setup workflows for Aceternity UI components.

Prerequisites:

• Node.js 18+ (for development and running the MCP server)
• npm (or yarn)
• Internet access to install dependencies from npm registry

Installation steps:

1. Clone the repository: git clone https://github.com/rudra016/aceternityui-mcp.git cd aceternityui-mcp

2. Install dependencies: npm install

3. Build the project (if the project uses a build step): npm run build

4. Run the MCP server locally: npm run dev

5. Verify the server is running. By default it should listen on the MCP transport interface (stdio-based) as described in the documentation. You can also run the built JS entry directly if you prefer: node dist/index.js

Note: If you plan to integrate with Claude, Cursor, Windsurf, Warp, or other MCP clients, you can also start the server using npx aceternityui-mcp or node path/to/aceternityui-mcp/dist/index.js depending on your setup.

Tips and common considerations:

• The MCP server relies on standard MCP tools: search_components, get_component_info, get_installation_info, list_categories, and get_all_components. Ensure your client uses the correct tool names and argument shapes.
• If you customize the environment, you may need to set environment variables for API endpoints or local data sources; these are not required for a standard setup but can be added in your deployment environment.
• For performance, consider prebuilding caches or using a persistent data store if your component catalog is large or frequently updated.
• When using npx aceternityui-mcp, ensure you have network access to fetch the package from npm during startup. In offline environments, prefer a local build and run workflow.
• If you encounter issues with Node version compatibility, ensure Node.js is at least v18.x and compatible with the project’s build tooling.