Posts and edits channel messages, opens direct messages, pins the important ones, and bulk-deletes spam in Revolt.
26actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro posts a message to a Revolt channel. Team members coordinate in real time without leaving the app.
Ayro retrieves a user's profile and contact details. Team members quickly find colleague information.
Ayro deletes a reaction from a message. Users undo accidental emoji reactions.
Each card is one request a support team gets, and the Revolt actions Ayro runs to close it.
Ayro resolves a user ID into an actual person, pulling their profile, bio, and account flags before it decides whether a request should be answered or escalated.
Ayro sends the update to the right channel, edits the same message when the details change, and marks it with a reaction so readers can see it has been handled.
Ayro removes a burst of unwanted posts in one bulk delete, strips the reactions that piled onto them, and blocks the account behind it.
When something needs a named owner, Ayro checks which channels are sitting unread, opens a DM with the person responsible, and pins the message so it stays findable.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Revolt actions it has and picks the ones a request needs.
Authorize the Revolt account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Revolt actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeRevolt · Ayro
What can you do in Revolt without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Revolt.
Bulk Delete Messages requires the ManageMessages permission regardless of who wrote the messages, and Remove Message Reaction needs it to clear anyone else's reactions. Without it, Ayro can still delete its own messages and remove its own reactions, so grant ManageMessages on the channels you want it to police.
All 26 actions your agent can call on Revolt, straight from the live MCP connection.
Acknowledge platform policy changes.
Add a reaction to a message in a channel.
Block another user by their ID.
Upload and save settings data to Revolt's sync storage.
Delete a message you've sent or one you have permission to delete.
Bulk delete multiple messages from a channel.
Fetch all bots that you have control over.
Fetch settings from server filtered by keys.
Fetch detailed information about a user.
Fetch flags associated with a specific user.
Fetch the server configuration for this Revolt instance.
Fetch a channel by its ID.
Retrieve your own user information.
Fetch detailed information about an invite by its code.
Fetch information about unread state on channels.
Retrieve a user's profile data including bio and background.
Fetch a user's default avatar image based on their ID.
Open a DM with another user.
Fetch all direct message conversations for the authenticated user.
Pin a message in a channel by its ID.
Remove a reaction from a message.
Send a message to a Revolt channel.
Unblock another user by their ID.
Unpin a message in a channel.
Edit a message that you've previously sent in a channel.
Update user information.
Same connection, same setup. Pick the next one your team already uses.
Provisions inboxes, lists and opens messages in full, and sends email from any address on the account.
Replies in channel and spins up threads, reads recent and pinned messages for context, grants member roles, and applies moderation actions on a report.
Reads the message log behind a delivery question, checks domain verification and API quota, and provisions SMTP users, tokens, and event webhooks.
Reads back what happened on a call, places outbound callbacks, keeps voice agent knowledge bases current, and batch tests an agent before it ships.
Creates and updates contact records, finds the thread a customer means with its channel and status, and keeps inboxes, labels, and webhooks accurate.
Reads space history, posts and targets messages, manages team and space membership, and registers webhooks in Webex.

Authorize the account and your agent has all 26 actions from the first conversation.
