AI helper for Spigot and Paper servers
Allay lives in your server’s chat. A player types /ask, and Allay looks into their real game—the inventory, the block under the crosshair, the chests around, this server’s recipes and plugins—before it answers.
An example of Allay answering in the game chat
⠹ Fluttering over the chests… (3s · ↑ 2,184 · ↓ 61 tokens)
/ask where did I put my redstone?
What players get
Allay reads the game through tools the plugin runs, so answers fit this player, this world, and this server.
“Which sword is better?” Allay reads the inventory, the block under the crosshair, statistics, and advancements instead of guessing.
“Where’s my redstone?” counts it in the inventory, the ender chest, and chests up to 32 blocks around, inside shulker boxes and bundles too.
The compass and a particle trail lead to a death point, a village, a cherry grove, a note, or a friend on the locator bar.
Sorting chests by category, smelting evenly, brewing in rounds, crafting at a real table. Agents work while you play, then report.
“Sword first, food in the last row.” Stacks merge, pinned slots get the best item, and [Put back] undoes it for 5 minutes.
Recipes, every brewing step, the cheapest anvil order, enchantments, and villager trades, one click under the answer.
“Why doesn’t my door open?” reads the machine and marks the fault. Experimental drafts show a build as ghost blocks, layer by layer.
Notes pinned to places, goals as a bar at the top of the screen, and reminders from 1 to 120 minutes.
Web search when a question needs it, and calculations at 64 significant digits: stacks, Nether coordinates, XP.
How to ask
Allay answers in the language of the question. While it works, the action bar shows what it’s doing, and a chat line appears for every tool it uses.
/ask <question>/askall <question>/askx <what to do>/allay chat sends what you write in chat to Allay. The first character decides where a line goes:
| You write | It goes |
|---|---|
how do I find netherite? | To Allay, privately, like /ask |
! give me a stack of torches | To Allay as commands, like /askx |
? where’s the nearest village? | To everyone, like /askall |
~ brb | To the ordinary chat |
Memory
Each player’s session keeps whole exchanges, tool results included, for 24 hours after the last question. “And how many were in that chest?” needs no second look.
Up to 30 short facts per player: where the base is, what they’re building, how they like answers. Allay saves them itself and says so.
/allay memory lists the facts, /allay forget erases them, and /allay new starts the conversation over.
Languages
The plugin’s texts come in five languages, picked by the country of the player’s IP address, then by the game’s language. /allay language picks one by hand.
The country database sits on your server: no address goes anywhere for the lookup. Allay answers in whatever language the question was asked.
Fair by design
Allay sees what the asking player could see, and gives regular players nothing they didn’t earn.
Game tools see the player who asked and the world around them. Other players appear only as the locator bar shows them: a name, a distance, a direction.
Tools that give items, teleport, or change the weather go to operators only, and the plugin checks three times.
Allay opens only containers the player could open, honors GriefPrevention claims, and never reveals a vanished player.
The admin panel never shows what anyone asked or what Allay answered, in any role. Keys and licenses never reach a log.
Install
The plugin talks to the hosted backend at allay.chat out of the box. You can also run your own.
Put allay-spigot.jar into plugins/ and restart the server.
As an operator, run /allay link for a subscription, or put your own OpenRouter key into provider.byok and run /allay reload.
Type /ask how do I craft a beacon? Asking “what can you do?” makes Allay explain itself.
Allay is on GitHub only for now. Modrinth and Hangar pages will follow; until then, take the jar from the releases.
Give PLUGINS the jar’s address, and the container fetches Allay itself.
services:
minecraft:
image: itzg/minecraft-server:java25
environment:
EULA: "TRUE"
TYPE: PAPER
VERSION: "26.3"
PLUGINS: |
https://github.com/allay-ai/minecraft/releases/latest/download/allay-spigot.jar
ports: ["25565:25565"]
volumes: ["./data:/data"]
Pricing
Every answer costs money at the model’s provider. Your server picks who pays.
Free
On allay.chat, with your provider’s bill.
Our key and our models, paid in Telegram Stars.
7 days
$0.75 of model costs
30 days, renews by itself
$3.00 of model costs
365 days
$6.00 of model costs every 30 days
/allay link as an operator/allay statusFree
Your backend, your key, no limits.
Self-hosting
Allay Server is open source and ships as one Docker image. With SELFHOSTED=1, billing is off and every question runs on your key.
compose.yaml, give every change-me a random value of its own, and run docker compose up -d.server.url in the plugin’s config.yml at your backend, give server.token the same PLUGIN_TOKEN, and run /allay reload./allay init for a one-time link to the admin panel, and paste your OpenRouter key there.services:
allay:
image: ghcr.io/allay-ai/server:6.0.0
restart: unless-stopped
depends_on: [allay-mongo, allay-redis]
# This machine only. Another machine reaches it through a reverse proxy with TLS.
ports: ["127.0.0.1:3000:3000"]
environment:
MONGODB_URI: mongodb://allay:change-me-mongo@allay-mongo:27017/?authSource=admin
MONGODB_DATABASE: allay
REDIS_URL: redis://:change-me-redis@allay-redis:6379
# Your own backend: no subscriptions, your plugins run on your key.
SELFHOSTED: "1"
# The plugin sends this as server.token; without it the backend answers no plugin. 24 characters or more.
PLUGIN_TOKEN: change-me-plugin-token
# Seals the keys you save in the admin panel. Keep it with your other secrets.
SECRETS_KEY: change-me
# The address you open in a browser; the panel's setup link starts here.
PUBLIC_URL: http://localhost:3000
allay-mongo:
image: mongo:8.0
restart: unless-stopped
environment:
MONGO_INITDB_ROOT_USERNAME: allay
MONGO_INITDB_ROOT_PASSWORD: change-me-mongo
volumes: [mongo:/data/db]
allay-redis:
image: redis:8-alpine
restart: unless-stopped
command: ["redis-server", "--save", "60", "1", "--requirepass", "change-me-redis"]
volumes: [redis:/data]
volumes:
mongo:
redis:
FAQ
Both, and their forks. It builds against the Spigot API. Furnace experience from agents goes to the player only on Paper; on Spigot it stays in the furnace.
No. Tools that give items or change the world go to operators only, and the plugin checks three times. Agents only move a player’s own things and craft from real ingredients. The one exception is [Take the book]: a written book with Allay’s own long answer, once.
Only what the asker’s locator bar shows: a name, a distance, and a direction. Whoever hides from the bar by crouching, a pumpkin, or invisibility hides from Allay too.
A session for 24 hours after the last question, up to 30 facts until the player erases them or stops asking for a year, numbers-only statistics under a pseudonym for 400 days, and full traces of a tenth of runs for 7 days. The privacy policy has the details. In the game, /allay privacy shows a player the same and erases it on request.
On a subscription, the model allay.chat picks, which the plugin can’t change. With your own key or your own backend, any model that can call tools; a server can even give each player tier its own model.
Yes. The plugin’s quota sets a monthly budget and splits it fairly by tiers you give with permissions. See limits per player.
Not yet. GitHub releases are the one source for now, and itzg/minecraft-server can fetch the jar from there.
Allay was MCBuddy until 4.0.0. The plugin moves your old folder, settings, and translations over by itself on the first start. See Coming from MCBuddy.
Allay runs on Moonlands, a hard survival server with friends. Join and ask it something.
minecraft.mairwunnx.com