Revolt
Revolt is a free and open-source chat platform offering secure and customizable communication.
Verdict
Common use cases
- Audit user accounts during moderation reviews
- Check role flags before assigning permissions
- Update profile fields for onboarding workflows
- Troubleshoot login issues by inspecting user status
- Bulk-check user badges for community events
Integration
- Vendor
- Revolt
- Category
- communication
- Auth
- API_KEY
- Tools
- 3
- Composio slug
revolt
Tools
- Fetch user
Tool to fetch detailed information about a user. use when you have a valid user id and need full account details. call after authenticating with bot token.
- Fetch User Flags
Tool to fetch flags associated with a specific user. use after obtaining the user id to inspect their special statuses or roles.
- Update User
Tool to update user information. use when you need to modify user profile or status fields. call after authenticating with bot token.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add MCP Server. 2. Select Revolt from the list and click Connect. 3. You'll be prompted to paste a Revolt bot token — generate one in your Revolt server settings under Bots > Create Bot, then copy the token. 4. Paste the token into Switchy and confirm the connection. 5. Switchy will verify the token and list the three available tools (Fetch User, Fetch User Flags, Update User). 6. To test, open any Space and type '@Revolt fetch user details for [user_id]' — replace [user_id] with a valid Revolt user ID from your server. 7. If the MCP returns profile data, the connection is live and you can invoke any tool by @mentioning Revolt in your prompts.
What teammates see: by default, memories from Revolt are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Audit User Account
@Revolt fetch the complete profile and all flags for user ID 01H8EXAMPLE123. Show me their account creation date, current status, and any special roles or badges they hold.Open in a Space →
Check Moderation Flags
@Revolt retrieve the flags for user ID 01H8EXAMPLE456. Tell me if they have any moderation history, verified status, or admin roles.Open in a Space →
Update User Status
@Revolt update user ID 01H8EXAMPLE789 to set their status message to 'On leave until March 15'. Confirm the change was applied successfully.Open in a Space →
Verify New Member
@Revolt get the profile for user ID 01H8EXAMPLENEW. Check their account age, username, and whether they have any existing flags or badges.Open in a Space →
Batch Role Check
@Revolt fetch flags for user IDs 01H8EXAMPLE001, 01H8EXAMPLE002, and 01H8EXAMPLE003. List which users have the 'Contributor' badge and are eligible for promotion.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Revolt show me the profile details for user ID 01FHKQM3XYZT8NQVR2JDCW9B5P including their current status and badges
Retrieved profile for user 01FHKQM3XYZT8NQVR2JDCW9B5P: Username is 'alex_dev', display name 'Alex Chen', currently online with status 'In a meeting until 3pm'. Account created March 2023, verified email. Active badges include Early Adopter and Server Booster. Avatar URL and banner color also returned. This illustrative example shows the kind of detailed account information the Fetch User tool provides when queried with a valid user ID.
This example demonstrates read access to user profiles. Requires a valid bot token with user read permissions. The user ID must exist in your Revolt instance — this won't work for arbitrary IDs outside your server's member list. Useful for building user directories or verification workflows.
@Revolt update my bot account's status message to 'Monitoring deployment pipeline' and set presence to idle
Successfully updated bot user profile. Status text changed to 'Monitoring deployment pipeline' and presence set to idle (yellow indicator). Changes are now visible to all server members who can see this bot. This illustrative example shows how the Update User tool modifies profile fields — actual response includes confirmation of which fields were changed and their new values.
This example shows write capability for the authenticated bot's own profile. You cannot modify other users' profiles unless your bot has elevated admin permissions. Status updates are immediate but presence changes may take a few seconds to propagate across all connected clients. Be mindful of rate limits when updating status frequently.
@Revolt check the flags for user 01FHKQM3XYZT8NQVR2JDCW9B5P and tell me if they have any special roles or restrictions I should know about
Fetched flags for user 01FHKQM3XYZT8NQVR2JDCW9B5P. Active flags: Verified (email confirmed), None for restrictions. No elevated permissions like Admin or Moderator detected at the user level. This user appears to be a standard member without special statuses. This illustrative example shows how flag inspection helps you understand a user's account standing — the AI can interpret the raw flag data and explain what it means for permissions or trust level.
This example pairs the Fetch User Flags tool with AI reasoning to translate technical flags into actionable context. Flags reveal account verification status, moderation history, and special roles. Requires the same user read permissions as profile fetching. Helpful for moderation workflows or conditional access logic based on user trust level.
Use-case deep-dives
When Revolt MCP makes sense for small Discord alternatives
A 6-person gaming studio runs their community on Revolt instead of Discord. They use Switchy to automate flag checks during moderation reviews—when a user is reported, the AI fetches their flags and recent activity, then drafts a warning or ban recommendation. This works because Revolt's API is simpler than Discord's and the studio already committed to the platform. The MCP's three tools cover the core loop: fetch user details, check flags, update status. If your community is under 500 members and you're already on Revolt, this is a clean fit. Above that size, you'll want batch operations the MCP doesn't expose yet. For teams still on Discord or Slack, don't migrate just to use this—stick with those MCPs instead.
Revolt MCP shines for gated community workflows
A 12-person DAO uses Revolt for private coordination. New members join via token-gated invites, and Switchy runs an onboarding flow: it fetches the new user's profile, checks their wallet-linked flags, then updates their display name and assigns initial roles based on token holdings. The MCP's update-user tool handles the profile edits without manual admin work. This scenario works because the DAO is small enough that three tools cover 80% of admin tasks, and Revolt's API key auth is simpler than OAuth for a bot-only use case. If your onboarding needs custom fields or multi-step approvals, you'll hit the MCP's tool ceiling fast. For communities under 100 active members with straightforward role logic, this is the right call.
When Revolt MCP isn't the right communication hub
A 4-person open-source maintainer team considers using Revolt for support requests instead of GitHub Discussions. They want Switchy to fetch user history and auto-tag repeat contributors. The MCP can pull user details and flags, but it has no message-search or channel-history tools—so the AI can't read past conversations or scan for duplicate questions. Revolt's strength is real-time chat, not threaded support archives. If your support flow is synchronous (live help desk hours), the MCP works for user lookups during active chats. But for async triage where you need to search message history or link related threads, GitHub or Linear MCPs are better fits. Use Revolt MCP only if your support is already happening in Revolt and you just need user-profile enrichment.
Frequently asked
What does the Revolt MCP do in Switchy?
The Revolt MCP lets your AI agents fetch and update user profiles on your Revolt server. It pulls account details, checks user flags (roles, badges, special statuses), and modifies profile fields. Think of it as giving your agents read-write access to your Revolt user directory without needing to write custom bot code.
Do I need a bot token to connect Revolt MCP?
Yes. Revolt uses API key authentication, which means you create a bot account in your Revolt server settings and paste its token into Switchy. The bot needs permissions to read user data and update profiles. Without those scopes, the MCP's tools will fail when called.
Can the Revolt MCP send messages or create channels?
No. This MCP only handles user account operations—fetching profiles, checking flags, updating user fields. If you need to send messages or manage channels, you'll have to use Revolt's REST API directly or wait for a separate messaging-focused MCP.
Why use the Revolt MCP instead of calling the Revolt API myself?
The MCP wraps Revolt's user endpoints in a format your AI agents understand natively. Instead of writing fetch logic and parsing JSON responses, you describe what you want in plain English and the agent calls the right tool. Faster for one-off tasks; less useful if you're building a full bot.
Who on my team should connect the Revolt MCP?
Whoever manages your Revolt server and can create bot accounts. That person generates the bot token, sets its permissions, and pastes the key into Switchy. Once connected, any team member with access to the Switchy workspace can invoke the MCP's tools through their agents.