Schema | HeroUI Migration MCP

HeroUI Migration MCP

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.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`resources`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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