Minecraft
Free Minecraft bot hosting.
For the bot, not the server. A headless client that logs into a world you already have, and stays logged in without a machine of your own switched on.
We host the bot. We do not host the server.
This is the thing to be clear about before you sign up. A Minecraft bot here is a program that connects out to a Minecraft server as if it were a player. The server itself has to be somewhere else — your own box, a game host, a friend's machine, whatever you already use.
25% of a CPU core and 256 MB of memory is a comfortable allocation for a client. It is nowhere near enough to run a world, and we would rather tell you that on this page than after you have uploaded a modpack.
Choose a runtime
Pick your language
All three are installed and tested. Each page covers the libraries, the deployment and what fits in 256 MB for that runtime specifically.
What people actually run here
AFK clients that hold a slot or keep chunks loaded. Chat bridges that relay between a server and somewhere else. Moderation helpers that watch chat and act on it. Automation that farms, builds or patrols. Monitoring that pings a server and reports when it goes quiet.
What these have in common is that they are small, long-running and mostly idle — which is exactly the shape a free allocation suits. A bot spending 23 hours a day waiting for an event costs almost nothing to keep online, and costs you a machine at home if you host it yourself.
Where the memory goes on a Minecraft bot
Unlike a chat bot, a Minecraft client builds a model of the world around it. Every chunk the server sends is decoded and held so the bot can reason about blocks, entities and its own position. That model, not your code, is what fills 256 MB.
The lever is view distance. A bot that only needs to read chat and type into it can run with the smallest view distance the server allows and barely register. A bot that pathfinds across terrain has to hold far more of the world, and that is where a free allocation starts to hurt.
Accounts, authentication and the honest warning
Connecting to a server in online mode means authenticating with a real Microsoft account, and that account is yours to look after. Offline-mode servers need no account at all, which is why most experimenting starts there.
Automating an account is against the rules of many public servers, and some of them ban for it. That is between you and the server you are joining. What we ask is narrower and is in the acceptable use policy: do not use a bot hosted here to grief, spam, crash or attack a server you have no permission to be on.
FAQ
Questions
Can I host my Minecraft server here instead?
No. This is bot hosting: 25% of a core and 256 MB of memory, which is a fine allocation for a client and not a usable one for a world. We are not a game server host and have no plan to become one.
Which version of Minecraft do bots support?
That depends entirely on the library you choose, not on us. We give you Node.js, Python or Bun and let you install what you like; whether it speaks the protocol version your server runs is a question for that library's documentation.
Will my bot stay connected when I close my laptop?
Yes, and that is usually the reason people move a bot off their own machine. It runs on our hardware, holds its connection around the clock, and restarts itself if it crashes. Your laptop has nothing to do with it once it is deployed.
Can the bot reconnect on its own when the server restarts?
If you write it to. Most libraries emit an event when the connection drops and let you reconnect after a delay. We restart the process if it exits, but a bot that stays running while disconnected is one only your code can fix.
Node.js, Python or Bun for a Minecraft bot?
Node.js, for most people. The headless-client ecosystem there is considerably more mature than Python's, and almost every Minecraft bot tutorial you find is written against it. Python is the better choice when your bot talks to a server from the outside rather than logging in as a player. Bun runs the same npm packages as Node.js with a faster start; if a library misbehaves under it, Node.js is the fallback.
Hosting something else?