convertJsFileToolName
Convert JavaScript files to TypeScript
LABSCO 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
USE CASES
01
Moving one file across to TypeScript
The conversion is scoped to a single path, so a migration advances file by file and each step is a diff someone can read before the next one starts.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"typescript-migrator-mcp": {
"command": "npx",
"args": [
"-y",
"typescript-migrator-mcp"
]
}
}
}npx
TERMINAL
npx -y typescript-migrator-mcp
