// MCP TOOL REFERENCE

HEROUI MIGRATION MCP TOOLS

18 tools from the HeroUI Migration MCP MCP Server, categorised by risk level.

// ALL 18 HEROUI MIGRATION MCP TOOLS

READ 16 tools

Read analyze_file Analyze code and return detailed findings about legacy imports, components, props, hooks and Tailwind patte... Read analyze_legacy_imports Quick heuristic scanner for HeroUI/NextUI v2 imports and symbols. Read analyze_tailwind_config Checks tailwind.config.js for legacy HeroUI plugins and content paths. Read audit_tailwind Analyze a Tailwind configuration file for legacy HeroUI patterns. Read check_v3_compatibility Checks if a file content follows HeroUI v3 patterns (no NextUI, uses compound API). Read compare_component Show presence/status of a component between v2 and v3, with alias lookup. Read corpus_status Checks the presence and metadata of generated documentation artifacts. Read diff_component Returns v2 and v3 (web) documentation for a specific component to help with migration. Read get_migration_guide (legacy) Returns detailed migration guidance for a component by comparing v2 and v3 docs. Read get_navbar_v3_backport Generates the TSX code for a HeroUI v3-compatible Navbar component (missing in v3). Read list_generated_v2_outputs Lists files present in data/generated after running the HeroUI v2 generator. Read list_generated_v3_outputs Lists files present in data/generated after running the HeroUI v3 generator. Read read_generated_v2_doc Reads one generated HeroUI v2 LLM output file. Read read_generated_v3_doc Reads one generated HeroUI v3 LLM output file. Read scan_project Recursively scans a directory for files using legacy HeroUI/NextUI components. Read resolve_alias Return canonical name and confidence for a legacy component name

WRITE 2 tools

Write rewrite_file Apply heuristic migrations to code and return the rewritten source plus diagnostics. Write migrate_file_code Applies heuristic transformations to convert HeroUI v2 code to v3 patterns.

// FAQ

How many tools does the HeroUI Migration MCP MCP server have? +

The HeroUI Migration MCP MCP server exposes 18 tools across 2 categories: Read, Write.

How do I enforce policies on HeroUI Migration MCP tools? +

Route the HeroUI Migration MCP server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do HeroUI Migration MCP tools fall into? +

HeroUI Migration MCP tools are categorised as Read (16), Write (2). Each category has a recommended default policy.

Enforce policy on every HeroUI Migration MCP tool call.

Start from HeroUI Migration MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.