@heroui/react-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 2 of 2 tools tried
Contacts while installing and starting: mcp-api.heroui.com
What it contacted
mcp-api.heroui.com
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @heroui/react-mcp@1.1.4
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 2 returned a result.
list_components | Returned a result 0.1 s · 945 characters |
get_theme_variables | Returned a result 0.3 s · 3,253 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
5 tools with commands in capitals or very long text
- Gives the agent orders in
list_components:t 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 s
- Gives the agent orders in
get_component_source_code: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 implem
- Gives the agent orders in
get_component_source_styles:ucture (e.g., .button, .button--accent, .button--disabled). IMPORTANT: These are framework-agnostic styles from @heroui/styles package. DO NOT mix BEM classes with React
- Gives the agent orders in
get_theme_variables:me documentation and guides, use the get_docs tool instead. IMPORTANT: HeroUI v3 uses Tailwind CSS v4 - ensure compatibility.
- Gives the agent orders in
get_docs:tarted, theming, colors, styling, animation, release notes. IMPORTANT: For component documentation, use get_component_docs instead. Example paths: /docs/react/getting-st
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
list_components
List 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_docs components
Get 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_code components
Get 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_styles components
Get 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_variables
Get 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_docs path
Get 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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.22.0 |
| Source | github.com/heroui-inc/heroui-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-h0DhQZLS74ykk0gdnXzuOdF+E2Ke/j1CuoJ8WSwemO4cFk8CJ5ASZJGA1CsErLC2urX1jZj+Zmfb2sjZ5u+XRQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40heroui/react-mcp)
New version out? Ask for a fresh report.