# How to integrate Revolt MCP with CrewAI

```json
{
  "title": "How to integrate Revolt MCP with CrewAI",
  "toolkit": "Revolt",
  "toolkit_slug": "revolt",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/revolt/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/revolt/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:24:12.121Z"
}
```

## Introduction

This guide walks you through connecting Revolt to CrewAI using the Composio tool router. By the end, you'll have a working Revolt agent that can fetch profile details for user by id, list all flags assigned to this user, update your status message to 'in a meeting' through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a Revolt account through Composio's Revolt MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Revolt with

- [OpenAI Agents SDK](https://composio.dev/toolkits/revolt/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/revolt/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/revolt/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/revolt/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/revolt/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/revolt/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/revolt/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/revolt/framework/cli)
- [Google ADK](https://composio.dev/toolkits/revolt/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/revolt/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/revolt/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/revolt/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/revolt/framework/llama-index)

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Revolt connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Revolt
- Build a conversational loop where your agent can execute Revolt operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

## What is the Revolt MCP server, and what's possible with it?

The Revolt MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Revolt account. It provides structured and secure access to your chat platform, so your agent can perform actions like retrieving user details, inspecting special user flags, and updating user profiles on your behalf.
- User profile retrieval: Instantly fetch detailed information about any user by providing a valid user ID, making it easy to manage accounts and view profile data.
- User flag inspection: Allow your agent to access and display special flags or roles associated with specific users, helping you understand permissions or statuses at a glance.
- User profile updates: Quickly update a user's profile or status fields directly from your agent, streamlining administrative and personalization tasks.
- Automated user management: Enable your agent to handle user account lookups and modifications, reducing manual effort and improving efficiency in managing your Revolt community.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `REVOLT_ACKNOWLEDGE_POLICY_CHANGES` | Acknowledge Policy Changes | Tool to acknowledge platform policy changes. Use when accepting or confirming policy updates for your bot account. |
| `REVOLT_ADD_CHANNELS_MESSAGES_REACTIONS` | Add Reaction to Message | Tool to add a reaction to a message in a channel. Use when you want to react with an emoji to a specific message. Returns success on completion. |
| `REVOLT_BLOCK_USER` | Block User | Tool to block another user by their ID. Use when you need to prevent interactions with a specific user. |
| `REVOLT_CREATE_SYNC_SETTINGS_SET` | Create Sync Settings | Tool to upload and save settings data to Revolt's sync storage. Use when you need to persist user settings or preferences. |
| `REVOLT_DELETE_MESSAGE` | Delete Message | Tool to delete a message you've sent or one you have permission to delete. Use when you need to remove a message from a channel. |
| `REVOLT_DELETE_MESSAGES_BULK` | Bulk Delete Messages | Tool to bulk delete multiple messages from a channel. Use when you need to delete multiple messages at once. Requires ManageMessages permission regardless of message ownership. Messages must have been sent within the past 1 week. |
| `REVOLT_FETCH_OWNED_BOTS` | Fetch Owned Bots | Tool to fetch all bots that you have control over. Use when you need to retrieve information about bots owned by the authenticated user account. |
| `REVOLT_FETCH_SYNC_SETTINGS` | Fetch Sync Settings | Tool to fetch settings from server filtered by keys. Returns an object with the requested keys where each value is a tuple of (timestamp, value). Only settings that exist on the server will be included in the response. |
| `REVOLT_FETCH_USER` | 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. |
| `REVOLT_FETCH_USER_FLAGS` | 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. |
| `REVOLT_GET_API_INFO` | Get API Info | Tool to fetch the server configuration for this Revolt instance. Use when you need to discover API version, feature availability, WebSocket endpoints, or service URLs. |
| `REVOLT_GET_CHANNEL` | Get Channel | Tool to fetch a channel by its ID. Use when you need to retrieve detailed information about a specific channel. |
| `REVOLT_GET_CURRENT_USER` | Get Current User | Tool to retrieve your own user information. Use when you need to fetch details about the authenticated user account. |
| `REVOLT_GET_INVITE` | Get Invite | Tool to fetch detailed information about an invite by its code. Use when you have a valid invite code and need to retrieve invite details including server info, channel info, and member count. |
| `REVOLT_GET_SYNC_UNREADS` | Get Sync Unreads | Tool to fetch information about unread state on channels. Use when you need to check which channels have unread messages or mentions. |
| `REVOLT_GET_USER_PROFILE` | Get User Profile | Tool to retrieve a user's profile data including bio and background. Use when you need profile-specific information beyond basic user data. Will fail if you do not have permission to access the target user's profile. |
| `REVOLT_GET_USERS_DEFAULT_AVATAR` | Get User's Default Avatar | Tool to fetch a user's default avatar image based on their ID. Use when you need to retrieve the default avatar picture for a specific user. |
| `REVOLT_GET_USERS_DM` | Open DM with User | Tool to open a DM with another user. Use when you need to start or access a direct message conversation. If the target is oneself, returns a saved messages channel. |
| `REVOLT_GET_USERS_DMS` | Get User DMs | Tool to fetch all direct message conversations for the authenticated user. Use when you need to list all DM and group DM channels. |
| `REVOLT_PIN_MESSAGE` | Pin Message | Tool to pin a message in a channel by its ID. Use when you need to highlight important messages for channel members. |
| `REVOLT_REMOVE_MESSAGE_REACTION` | Remove Message Reaction | Tool to remove a reaction from a message. Use when you need to remove your own, someone else's, or all reactions of a given emoji from a message. Requires ManageMessages permission if removing others' reactions. |
| `REVOLT_SEND_CHANNELS_MESSAGES` | Send Channel Message | Tool to send a message to a Revolt channel. Use when you need to post a text message, embed, or attachment to a specific channel. Call after authenticating with bot token. |
| `REVOLT_UNBLOCK_USER` | Unblock User | Tool to unblock another user by their ID. Use when you need to remove a block on a specific user. The relationship status will change from 'Blocked' to 'None' after successful execution. |
| `REVOLT_UNPIN_MESSAGE` | Unpin Message | Tool to unpin a message in a channel. Use when you need to remove a pinned message from the channel's pinned messages list. |
| `REVOLT_UPDATE_CHANNELS_MESSAGES` | Update Channel Message | Tool to edit a message that you've previously sent in a channel. Use when you need to update the content or embeds of an existing message. At least one of content or embeds must be provided. |
| `REVOLT_UPDATE_USER` | Update User | Tool to update user information. Use when you need to modify user profile or status fields. Call after authenticating with bot token. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Revolt MCP server is an implementation of the Model Context Protocol that connects your AI agent to Revolt. It provides structured and secure access so your agent can perform Revolt operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Python 3.9 or higher
- A Composio account and API key
- A Revolt connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to Revolt via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived Revolt MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for Revolt

**What's happening:**
- You create a Revolt only session through Composio
- Composio returns an MCP HTTP URL that exposes Revolt tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["revolt"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["revolt"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to Revolt through Composio's Tool Router. The agent can perform Revolt operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build Revolt MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/revolt/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/revolt/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/revolt/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/revolt/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/revolt/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/revolt/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/revolt/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/revolt/framework/cli)
- [Google ADK](https://composio.dev/toolkits/revolt/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/revolt/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/revolt/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/revolt/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/revolt/framework/llama-index)

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication.
- [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack.
- [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers.
- [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity.
- [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease.
- [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace.
- [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms.
- [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates.
- [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices.
- [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels.
- [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks.
- [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission.
- [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security.
- [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Revolt MCP?

With a standalone Revolt MCP server, the agents and LLMs can only access a fixed set of Revolt tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Revolt and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Revolt tools.

### Can I manage the permissions and scopes for Revolt while using Tool Router?

Yes, absolutely. You can configure which Revolt scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Revolt data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)