Summary

The parameter discovery is what makes running a bot from chat workable.

Asking a project for its required and optional parameters before launching it means the assistant can prompt you for what is missing instead of failing mid-run — and the returned defaults tell you what happens if you leave one out. The refusal to start a second run while one is in flight is the other detail that matters in practice, since RPA runs drive a real desktop.

What it is

A TypeScript MCP server for AntBot, an AI-based RPA platform. It reads project definitions from your local AntBot Robot install and lets a client trigger runs with parameters.

What you get

`Get_AntBot_Project_List` — the projects available from the AntBot manager
`Get_AntBot_Project_Info` — one project's detail, including required and optional parameters with their types and default values
`Run_AntBot_Project` — starts a project with a parameters object, given its id and path
`Get_Last_Mcprun_Log` — the last 100 lines of the newest mcprun log, for seeing what a run actually did
Duplicate-run protection: the server checks for a live AntBot Runner process and refuses to start a second one
Project caching, so repeated lookups do not re-parse the configuration each time

Requirements

Windows, because the running-process check uses the Windows task list. Node.js v16 or newer, `npm install` and `npm run build`. AntBot Robot must be installed and linked to the manager, with its configuration file present at `%APPDATA%\Roaming\AntBotRobot\AntBot_Robot.exe.config` — the server loads its settings from there automatically.