HextaUI Pro MCP server

• Addresshttps://hextaui.com/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on hextaui.com when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-27
• Tools8
• Server calls itselfhextaui
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 138 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer817 ms
• Space in an agent's context≈ 1,234 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_docs

  Search HextaUI components, hooks, utilities, examples, props and data attributes. Use plain language or a prop name, e.g. 'confirm before delete', 'chat message list', 'loading button' or 'onOpenChange'. Returns ranked matches with the…

• list_components

  List every HextaUI component, hook and utility with a one-line description, grouped by category. Filter by kind or category to keep the list short.

• get_component

  Full docs for one component, hook or utility: what it is for, the install command, usage, examples, keyboard support, accessibility notes and the API reference. Read this before using a component.

• get_component_api

  Only the API of a component: how its parts nest, every part with its props, types, defaults and data attributes, and keyboard support. Cheaper than get_component when you already know what the component does.

• get_component_source

  The source files of a component, hook or utility exactly as the shadcn CLI installs them, with their npm and HextaUI dependencies. Prefer installing with get_install_command; use this to read how something works or to copy it by hand.

• get_examples

  Working example code for a component, taken from its docs. Without `examples` it returns the main demo and lists the other examples by name. Pass names from that list, or from get_component, to get their code.

• get_install_command

  One shadcn CLI command that installs several HextaUI components, hooks or utilities into the user's project, with the theme tokens and every dependency. Run it in the project root.

• get_setup

  How to add HextaUI to a project: requirements, the shadcn CLI, the @hextaui namespace, theme tokens for manual installs, and the conventions generated code should follow. Use this when the project has no HextaUI components yet.