Let an AI assistant such as Claude Code drive your Asterobot through MCP, and know what it can do, what it can't, and what to keep in mind before you let it.
Asterobot can be driven by an AI assistant, the way you drive it from Asteroboard. The assistant connects to Asterobot, sees everything Asteroboard can do as a list of tools, and calls them while you talk to it: "add a bot on my second account and connect it", "which tables hold the monsters and their drops", "write a script that greets the guild when the bot signs in". This chapter explains what an assistant gets, how to connect one, and what to watch out for.
What MCP is
MCP, the Model Context Protocol, is the standard way assistants talk to programs. Asterobot speaks it at the address /mcp, right next to the address Asteroboard uses. Any assistant that supports MCP over HTTP can connect: Claude Code, Codex, Cursor, a desktop assistant, or a program of your own. Nothing in Asterobot is tied to one of them, and there's nothing to install on Asterobot's side: it's on as soon as Asterobot starts.
What an assistant can do
Asteroboard does everything through Asterobot's port, and an assistant gets the same port. So it can do what you do on every page of Asteroboard:
- Ankama accounts: add one, sign it in automatically or by hand, answer the code Ankama sends, refresh or check a sign-in, disconnect it.
- Bots: add, change and delete bots, connect and disconnect them, answer a connection question, move the character on its map, take it to the next map by a side, use a door, a zaap, a resource or an exit of its map, read a bot's console, choose which messages the bot mirrors, and send a message on its socket.
- Packages: install a package from the marketplace when you give it the file's id, create a package, edit its script and manifest, load, play, stop and reload it, read and change its settings, click its actions, update it, delete it.
- Fights: switch a bot's fight module on or off, choose its profile, speed and the fights it plays, read its turn log, and make, change, import and delete fight profiles.
- Game: list, download, extract, verify and uninstall game versions, browse the game data tables, look up texts and names, and run SQL queries.
- Everything else: read and change settings, manage proxies, sign Asterobot in and out of asterobot.net, check that Asterobot answers, and follow what happens through events and the log.
Each tool is one action of Asterobot, named after what it does: get-bots lists your bots, post-bot-connect connects one, put-config-key changes a setting. There are about a hundred of them. The assistant reads a short description with each, written for it, so you don't have to explain Asterobot to it. When it starts something that takes time, such as connecting a bot, the answer tells it which event to wait for, and it can watch that event with a tool made for that. Tools, events and limits has the details.
What it can't do
- Shut Asterobot down or reset every setting. These two actions are hidden from assistants unless you allow them in the settings. See MCP settings.
- Export or import a package as a zip file. Those need a file on your computer, which an assistant doesn't handle. Installing from the marketplace, and creating or editing a package in place, work.
- Browse the marketplace. It can install a package when you give it the file's id or address from asterobot.net, but it has no way to search the marketplace itself.
- More than a script can. An assistant writes and runs the same scripts you'd write: they can move on a map, change map, use the elements of a map and talk to the game, and they meet the same limits, described in What scripts can do.
- Anything Asterobot refuses. When your asterobot.net account doesn't give Asterobot access to the game protocol, the tools that need it answer that the game engine isn't available, exactly as Asteroboard would show it.
Note
Coming soon. The assistant can't read this documentation through Asterobot yet. Until then it works from what each tool says about itself, from the script reference it can fetch, and from what it already knows about Dofus. You can paste a page of these docs into the conversation when it needs one.
Keep in mind
An assistant acts as you. Whatever you can do from Asteroboard, it can do, on your Ankama accounts and with your asterobot.net account. Security lists what that covers.
Most assistants ask before changing something. Every tool says whether it only reads. Assistants such as Claude Code ask for your permission before a tool that changes something, and let you allow a tool once or for good. Look at what a tool is about to do before you allow it, the same way you'd read a dialog before clicking OK.
It reads what other people write. A bot's console and traffic carry chat messages from other players. An assistant that reads them could take a message written to trick it for an instruction. Asterobot doesn't filter that. Keep the permission prompts on for tools that change things, and don't leave an assistant running unattended on a bot in a busy chat.
Secrets stay hidden. Tool answers never contain website.token or your basic auth passwords, even through the settings tools: those values are replaced with [redacted].
Next: Connect an assistant.