Bots for your community
Built-in, private and AI-native. Automate your server with webhooks and triggers, post interactive cards, and let AI assistants like Claude work as bots — no separate account or hosting.
Three ways to build a bot
From a one-line webhook to a full AI assistant. Pick the level that fits.
Incoming webhooks
Send messages into a channel from anything that can POST JSON — CI/CD, monitoring, your own scripts. Rich cards, colors and file attachments included.
Webhook docsTriggers & buttons
Turn a /command into a webhook, no code. Reply with interactive buttons and live-updating cards for approvals, menus and status.
Bot messagesAI assistants (MCP)
A built-in MCP server lets Claude and other AI tools read and act in your chats — 77 permissioned tools, running locally. Discord has no equivalent.
MCP guideWhat you can build
A few of the things communities and teams run on mssgs bots.
Standups & reminders
Post the daily standup, nudge people about deadlines, run recurring check-ins.
Monitoring & CI/CD
Deploy status, build results, uptime and error alerts — straight into the right channel.
Moderation helpers
Approval flows, report queues and one-tap actions with interactive buttons.
AI copilots
Let Claude answer questions, summarise a channel or act as a bot — via MCP.
Fun & games
Polls, trivia, custom commands and little bots that make your server yours.
Connect any tool
GitHub, Unifi and anything else that speaks webhooks, plus a full REST API.
More than a message-posting bot
Everything you build with a typical chat bot, plus an AI layer and privacy by default.
Built in, no hosting
No third-party bot to invite, no server to keep running. Bots are part of mssgs.
AI-native
A built-in MCP server so Claude and other AI tools work as first-class bots.
Private by design
You choose the channels a bot sees; the AI server runs locally with revocable tokens.
No code, or full code
Visual triggers for the simple stuff, a REST API and webhooks when you want more.
Create your own bot account
Spin up a bot account in a minute — verify your email, agree to the rules, and get a token. It is created here and linked to your main account.
By creating a bot you agree to the Development Rules & Terms.
Frequently asked questions
Yes. Bots are built into mssgs — post rich cards, run interactive buttons and automate your server with webhooks and triggers, and connect AI assistants like Claude over MCP. No separate bot account or hosting needed. See the developer docs.
With Discord you invite a third-party bot and usually host it yourself. mssgs bots are built in and run locally, you choose exactly which channels they see, and there is a native AI layer (MCP) that Discord has no equivalent for. See the mssgs vs Discord comparison.
No. Custom triggers let you turn a /command into a webhook visually, with no code. When you do want to build something richer, there is a full REST API, webhooks and interactive bot messages — all in the docs.
Yes. The desktop app ships a built-in MCP server, so Claude, Cursor and other AI tools can read and act in your chats through 77 permissioned tools. Read the MCP guide.
You pick exactly which channels a bot or AI assistant can see, and the MCP server runs locally on your own machine with revocable tokens. Nothing else in your account is exposed.
Daily standups and reminders, monitoring and CI/CD alerts, moderation helpers, approval flows with buttons, AI copilots, and integrations with any tool that can send a webhook.