Scan VBScript for migration risks (free) and convert it to PowerShell with a review list.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Converts a VBScript script to idiomatic PowerShell (Windows PowerShell 5.1 by default, or PowerShell 7), preserving behaviour, exit codes and side effects, replacing COM objects with native cmdlets where possible. Returns JSON: the PowerShell code, a review checklist of warnings (AI warnings + automatic static-scan findings), blockers, security flags and the risk score. The result is a draft for human review and testing, not a guaranteed drop-in replacement.
VBScript source code (max 30000 characters).
Target PowerShell version. Default: ps51 (Windows PowerShell 5.1, preinstalled).
Optional: how the script is run (logon script via GPO, scheduled task, SCCM/Intune, manual) and anything the converter should know (max 1000 characters).
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http vbs-migrate-mcp https://vbs-migrate-mcp.lamtoueqali.workers.dev/mcp
Tool list last changed Nov 22, 2026.
Converts a VBScript script to idiomatic PowerShell (Windows PowerShell 5.1 by default, or PowerShell 7), preserving behaviour, exit codes and side effects, replacing COM objects with native cmdlets where possible. Returns JSON: the PowerShell code, a review checklist of warnings (AI warnings + automatic static-scan findings), blockers, security flags and the risk score. The result is a draft for human review and testing, not a guaranteed drop-in replacement.
| Argument | Type | Description |
|---|---|---|
| code* | string | VBScript source code (max 30000 characters). |
| target | string | Target PowerShell version. Default: ps51 (Windows PowerShell 5.1, preinstalled). |
| context | string | Optional: how the script is run (logon script via GPO, scheduled task, SCCM/Intune, manual) and anything the converter should know (max 1000 characters). |
{
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "VBScript source code (max 30000 characters)."
},
"target": {
"enum": [
"ps51",
"ps7"
],
"type": "string",
"description": "Target PowerShell version. Default: ps51 (Windows PowerShell 5.1, preinstalled)."
},
"context": {
"type": "string",
"description": "Optional: how the script is run (logon script via GPO, scheduled task, SCCM/Intune, manual) and anything the converter should know (max 1000 characters)."
}
}
}FREE. Returns the download link and usage instructions for VBS Readiness, a free read-only PowerShell scanner (Windows 10/11) that finds every VBScript dependency on a PC or share (files, scheduled tasks, Run keys, Group Policy scripts, executions logged as event 4096) and new-Outlook blockers (COM add-ins, VBA macros, PST files). Use it when a user needs to inventory VBScript before Windows disables it, then convert the scripts found with convert_vbscript_to_powershell.
No arguments.
{
"type": "object",
"properties": {}
}FREE and instant. Returns the PowerShell replacement for a VBScript COM ProgID (e.g. "Scripting.FileSystemObject", "MSXML2.XMLHTTP", "Outlook.Application"), a GetObject moniker ("winmgmts:", "LDAP://") or a VBScript function/statement ("Mid", "InStr", "On Error Resume Next", "Select Case", "MsgBox"), with migration notes.
| Argument | Type | Description |
|---|---|---|
| query* | string | ProgID, moniker or VBScript keyword/function. |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "ProgID, moniker or VBScript keyword/function."
}
}
}FREE and instant (no AI). Static migration-readiness scan of a VBScript file (.vbs, .wsf, HTA or classic ASP snippet) before Windows disables VBScript: lists COM objects used (FileSystemObject, WScript.Shell, ADODB, XMLHTTP, WMI, Outlook, Excel...) with their PowerShell equivalent, risky features (On Error Resume Next, Execute/Eval, SendKeys, registry, MsgBox), conversion traps (1-based strings, array bounds, case-sensitive comparisons, ByRef), blockers, security flags (hard-coded passwords, plain HTTP) and a 0-100 risk score with difficulty. Use it to triage many scripts before converting.
| Argument | Type | Description |
|---|---|---|
| code* | string | VBScript source code (max 30000 characters). |
{
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "VBScript source code (max 30000 characters)."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 22, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.
What changed in this server's tools since we started watching, newest first. Each change is scanned again.
FREE. Returns the download link and usage instructions for VBS Readiness, a free read-only PowerShell scanner (Windows 10/11) that finds every VBScript dependency on a PC or share (files, scheduled tasks, Run keys, Group Policy scripts, executions logged as event 4096) and new-Outlook blockers (COM add-ins, VBA macros, PST files). Use it when a user needs to inventory VBScript before Windows disables it, then convert the scripts found with convert_vbscript_to_powershell.