Halobot gives any MCP-capable agent a Discord communication channel. Agents ask questions, wait for your reply, and keep working — from your phone, desktop, wherever.
Human-Agent Loop Over Bot
Your agent is three hours into a refactoring task. It hits an ambiguous requirement. What does it do? It guesses. It picks the wrong interpretation. It builds 400 lines of code on a bad assumption. You come back, see the mess, and start over.
Halobot sits between your agent and Discord. Your agent calls an MCP tool. You get a notification. You reply. Done.
No new app. Your agent's messages show up alongside everything you already check.
Each agent gets its own thread. Three agents running? Three separate threads. No cross-talk.
No Twilio fees. No Slack Enterprise license. No per-message pricing. Discord bots cost nothing.
Desktop, mobile, web. Push notifications on all of them. Your agent reaches you wherever you are.
High-level tools handle thread conversations — the 90% use case. Low-level tools give you raw Discord access when you need it.
send_thread_message
Send a message via a Discord thread (creates new or continues existing)
wait_for_reply
Wait for the human to reply in a thread
send_and_wait
Send + wait in one call — best for simple Q&A
list_conversations
List all active thread conversations
get_thread_messages
Fetch full message history from a thread
list_guilds
List all servers the bot is in
list_channels
List text channels in a guild
send_message
Send a message to any channel
read_messages
Read recent messages from the in-memory cache
get_channel_history
Fetch paginated message history via API
wait_for_message
Poll until a matching message arrives
One command gets you through interactive setup — creates the bot, validates permissions, and configures your MCP client.
npm install -g halobot
npx halobot setup
Walks you through bot creation with clickable links, validates everything, and configures Claude Code automatically.
claude mcp add discord -- halobot
halobot doctor
Validates bot token, permissions, channel config, and user whitelist before your agent tries to send a message.
The thread model works for more than asking questions. Every pattern keeps the agent autonomous and you in control.
Agent hits an ambiguous requirement, asks which approach to take. You reply "option 2" from your phone.
Agent reaches a deploy step, waits for your explicit "go" in Discord before continuing. No more 3 AM deploys.
Agent posts status to the thread as it works. You check in when convenient — not when the agent demands it.
Multiple agents, each with their own thread, all reaching the same human. You're the hub, Discord is the switchboard.
Agent posts what it tried, asks for your intuition, incorporates your response, tries again. Async pair programming.
Only approved Discord users can interact with agent threads. Random server members can't hijack your workflow.
Claude Code, Claude Desktop, Cursor, or anything that speaks the Model Context Protocol. The agent doesn't know Discord is involved.
npx halobot setup walks through everything interactively with clickable links. No manual config editing.
halobot doctor validates your entire setup before your agent ever tries to send a message.
Long messages — code diffs, error logs — split automatically across Discord's 2000-char limit. Nothing gets truncated.
Each agent interaction gets its own Discord thread. Clean, organized, no cross-talk between agents.
Swap Discord for Slack tomorrow — only the MCP server changes. Your agent's code stays the same.
Set it up once, and your agents will never have to guess again.