All servers / Design / HeroUI MCP server
HeroUI MCP server
MCP server for HeroUI component documentation via Model Context Protocol
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.1.4. Package: @heroui/react-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (7.5 seconds including download)
- Tools offered: 6
- Last published: 2026-11-03
- Weekly downloads (npm): 8,171
- License: MIT · Direct dependencies: 7
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_componentsno parametersList all available components in HeroUI v3 - v2 components NOT supported. ⚠️ VERSION INFO: This returns v3 components only - NOT v2 components. Migration from v2 is available - visit https://heroui.com/docs/react/migration. If you need v2 components, visit https://v2.heroui.com (not supported by this MCP). Always call this first before using any component to verify it exists in v3. Returns the component names exactly as they should be used in imports and other tool calls. v3 uses compound patterns (e.g., Card.Header, Card.Content) - different from v2's flat props. Example workflow: list_components → get_component_docs → get_component_source_code (optional).
get_component_docs1 of 1 parameter describedGet complete component documentation (including examples, props, usage) directly from heroui.com. Accepts an array of component names and returns the full MDX documentation for each component. Returns raw markdown content from the component's .mdx file, which includes: - Import statements - Usage examples - Variants and sizes - Props documentation - Styling information - API Reference - And more This tool replaces get_component_info, get_component_props, and get_component_examples. Use this when you need complete component documentation in one call. Workflow: list_components → get_component_docs.
get_component_source_code1 of 1 parameter describedGet the actual React/TypeScript source code implementation of HeroUI v3 components. Accepts an array of component names and returns source code for each. Returns the internal implementation for learning purposes or debugging. Shows how the component is built using React Aria Components. Use this to understand component internals, not for copying implementation. The source shows accessibility features, keyboard handling, and ARIA attributes. Note: For using components, refer to examples via get_component_docs. IMPORTANT: Do NOT copy this code directly - use the component via @heroui/react imports. This shows v3 implementation which uses React Aria Components as foundation. GitHub links are provided for viewing the source in context.
get_component_source_styles1 of 1 parameter describedGet the CSS styles and BEM classes for HeroUI v3 components. Accepts an array of component names and returns styles for each. Returns the complete CSS implementation including all variants and states. Shows BEM class structure (e.g., .button, .button--accent, .button--disabled). IMPORTANT: These are framework-agnostic styles from @heroui/styles package. DO NOT mix BEM classes with React components - choose one approach: - Use @heroui/react for full React components with accessibility - Use @heroui/styles for CSS-only styling without JavaScript BEM classes provide styling only - no JavaScript behavior or accessibility. For production use, prefer @heroui/react components for full functionality. GitHub links are provided for viewing styles in context.
get_theme_variablesno parametersGet HeroUI v3 default theme variables and design tokens (actual variable values). Includes both light and dark mode variables for all categories: - Colors: Color tokens (accent, success, danger, background, foreground) - Typography: Font sizes, weights, line heights - Spacing: Margin, padding, gap values - Borders: Border radius, widths, colors - Shadows: Box shadows and elevations - Animations: Durations, timing functions Variables use modern oklch() color format for better color manipulation. Apply these in your CSS with :root or theme-specific selectors. Example variables: --color-accent, --radius-md, --font-size-body, --spacing-4. For theme documentation and guides, use the get_docs tool instead. IMPORTANT: HeroUI v3 uses Tailwind CSS v4 - ensure compatibility.
get_docs1 of 1 parameter describedGet HeroUI v3 React documentation content for guides, principles, and release notes (NOT component docs). Fetches official documentation from heroui.com. Returns the complete MDX content of documentation pages. Use for understanding concepts, design principles, implementation guides, and version history. Documentation covers: getting started, theming, colors, styling, animation, release notes. IMPORTANT: For component documentation, use get_component_docs instead. Example paths: /docs/react/getting-started/theming, /docs/react/releases/v3-0-0-rc-1. All React documentation paths start with /docs/react/ prefix. Returns MDX content which may include code examples and explanations. This is v3 documentation - ensure you're working with HeroUI v3, not v2. NOTE: For HeroUI Native documentation, use the @heroui/native-mcp server instead.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.