All servers / Design / HeroUI Native MCP server
HeroUI Native MCP server
MCP server for HeroUI Native 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/native-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 (6.5 seconds including download)
- Tools offered: 4
- Last published: 2026-11-03
- Weekly downloads (npm): 2,442
- License: MIT · Direct dependencies: 6
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 Native. Returns the component names exactly as they should be used in imports and other tool calls. HeroUI Native components are React Native components for mobile development. Always call this first before using any component to verify it exists. Example workflow: list_components → get_component_docs.
get_component_docs1 of 1 parameter describedGet complete HeroUI Native 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. Note: Examples are included in the component docs, no separate examples tool needed.
get_theme_variablesno parametersGet HeroUI Native default theme variables and design tokens (actual variable values). Returns organized CSS custom properties that control the entire design system. Variables follow a three-layer system: primitives → semantic → calculated. 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 HSL 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 Native uses Uniwind (Tailwind CSS for React Native) - ensure compatibility.
get_docs1 of 1 parameter describedGet HeroUI Native 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/native/getting-started/theming, /docs/native/releases/v1-0-0. All Native documentation paths start with /docs/native/ prefix. Returns MDX content which may include code examples and explanations. This is documentation for HeroUI Native.
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.