// SCAN REPORT

HeroUI Migration MCP

18 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

2 can modify or destroy data

16 read-only

18 tools total

Community server · catalogue entry verified 11/06/2026

How to control HeroUI Migration MCP ↓

TOOL MAP

What HeroUI Migration MCP exposes to your agents

Read (16) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous HeroUI Migration MCP tools

Write · Medium migrate_file_code The tool transforms and updates source code (reversible modifications). Write · High rewrite_file This tool modifies source code by applying heuristic migrations and returning rewritten content.

2 of HeroUI Migration MCP's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control HeroUI Migration MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and HeroUI Migration MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "rewrite_file": {
    "limits": [
      {
        "counter": "rewrite_file_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_file": {
    "limits": [
      {
        "counter": "analyze_file_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register HeroUI Migration MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON HEROUI MIGRATION →

Free to start. No card required.

FULL CATALOGUE

All 18 HeroUI Migration MCP tools

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.

READ 16 tools

Read analyze_file Analyze code and return detailed findings about legacy imports, components, props, hooks and Tailwind patterns 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

FAQ

Questions about HeroUI Migration MCP

How do I prevent bulk modifications through HeroUI Migration MCP? +

The HeroUI Migration MCP server has 2 write tools including rewrite_file, migrate_file_code. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach HeroUI Migration MCP.

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

18 tools across 2 categories: Read, Write. 16 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on HeroUI Migration MCP? +

Register the HeroUI Migration MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every HeroUI Migration MCP tool call.

Deterministic rules across all 18 HeroUI Migration MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HEROUI MIGRATION →

Free to start. No card required.

18 HeroUI Migration MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.