Get_AntBot_Project_ListLABSCO 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 managerGet_AntBot_Project_Info— one project's detail, including required and optional parameters with their types and default valuesRun_AntBot_Project— starts a project with a parameters object, given its id and pathGet_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.
Setup effort
Build from source — git clone https://github.com/jinwon-antbotcore/antbot-mcp-server.git
USE CASES
01
Running an automation without opening AntBot
List the projects, read the one you want, and start it with the parameters it asked for.
02
Finding out why a run did nothing
Pull the tail of the newest mcprun log and read what the run reported.
03
Working out what a project needs before you commit
Read the project info and check the parameter summary rather than guessing at the arguments.
4 tools
Listed in project docs. Your client may show a different list.
Get_AntBot_Project_InfoRun_AntBot_ProjectGet_Last_Mcprun_LogBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js v16 or later (LTS recommended)
- Windows (the server checks for the AntBot Runner process)
- AntBot Robot installed and linked to the manager
- AntBot Robot config file present: %APPDATA%\Roaming\AntBotRobot\AntBot_Robot.exe.config
- Claude Desktop installed
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
# Clone the project
git clone https://github.com/jinwon-antbotcore/antbot-mcp-server.git
cd antbot-mcp-server
# Install dependencies
npm install
# Build
npm run build
# Or a clean build (deletes the existing build files, then rebuilds)
npm run cleanbuildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"antbot-mcp-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_ANTBOT_MCP_SERVER>\\build\\index.js"
]
}
}
}
