Summary
It converts one file per call, which is what keeps a migration reviewable rather than a single unreadable diff.
The tool takes a filePath and nothing else, so a migration advances as a sequence of changes someone can actually read. There is no reporting of what changed and no check on the result — conversion is the entire surface, and verification stays with your type checker.
What it is
A single-tool converter: a JavaScript file path goes in and its TypeScript equivalent comes out.
What you get
- convertJsFileToolName, which converts the JavaScript file at a given filePath to TypeScript.
Requirements
Nothing to supply — no account, no key. A JavaScript file the server can reach by path.
Setup effort
One command — npx -y typescript-migrator-mcp