HeroUI Migration MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEGACY_TOOLS_ENABLED | No | Enables older compatibility and debugging tools that are not enabled by default. Set to 'true' to enable. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| corpus_statusB | Checks the presence and metadata of generated documentation artifacts. |
| scan_projectB | Recursively scans a directory for files using legacy HeroUI/NextUI components. |
| analyze_fileC | Analyze code and return detailed findings about legacy imports, components, props, hooks and Tailwind patterns. |
| rewrite_fileC | Apply heuristic migrations to code and return the rewritten source plus diagnostics. |
| compare_componentB | Show presence/status of a component between v2 and v3, with alias lookup. |
| audit_tailwindB | Analyze a Tailwind configuration file for legacy HeroUI patterns. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sctg-development/heroui-migration-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server