# How to integrate Slite MCP with CrewAI ```json { "title": "How to integrate Slite MCP with CrewAI", "toolkit": "Slite", "toolkit_slug": "slite", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/slite/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/slite/framework/crew-ai.md", "updated_at": "2026-03-29T06:50:56.164Z" } ``` ## Introduction This guide walks you through connecting Slite to CrewAI using the Composio tool router. By the end, you'll have a working Slite agent that can search all notes about onboarding process, create a new note in project channel, summarize recent updates from team docs through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Slite account through Composio's Slite MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Slite with - [OpenAI Agents SDK](https://composio.dev/toolkits/slite/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/slite/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/slite/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/slite/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/slite/framework/codex) - [OpenClaw](https://composio.dev/toolkits/slite/framework/openclaw) - [Hermes](https://composio.dev/toolkits/slite/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/slite/framework/cli) - [Google ADK](https://composio.dev/toolkits/slite/framework/google-adk) - [LangChain](https://composio.dev/toolkits/slite/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/slite/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/slite/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/slite/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Slite connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Slite - Build a conversational loop where your agent can execute Slite 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 Slite MCP server, and what's possible with it? The Slite MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Slite account. It provides structured and secure access so your agent can perform Slite operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SLITE_ASK_QUESTION` | Ask Question | Tool to ask a question to your Slite notes in natural language. Use when you need to query or search information across your notes. Supports optional filters to narrow results by parent note or specific assistant. | | `SLITE_CREATE_NOTE` | Create Note | Tool to create a note from markdown or HTML content with optional template. Use when you need to create a new note in Slite with specified content and title. | | `SLITE_DELETE_NOTE_BY_ID` | Delete Note By ID | Tool to permanently delete a note and all its children by ID. Use when you need to remove a note irreversibly. This operation cannot be undone. | | `SLITE_FLAG_NOTE_AS_OUTDATED` | Flag Note as Outdated | Tool to set Outdated status on a note with a reason. Use when you need to flag a note as containing outdated information. | | `SLITE_GET_AUTHENTICATED_USER` | Get authenticated user | Retrieves information about the currently authenticated user. Use this to get user details including email, display name, and organization information. | | `SLITE_GET_NOTE_BY_ID` | Get Note By ID | Tool to retrieve a complete note by its ID including content in Markdown or HTML format. Use when you need to fetch the full details and content of a specific note. | | `SLITE_GET_NOTE_CHILDREN` | Get Note Children | Tool to retrieve note children by parent note ID. Use when you need to fetch child notes beneath a specified parent note. Supports pagination for notes with more than 50 children using cursor-based navigation. | | `SLITE_LIST_NOTES` | List Notes | Tool to list notes from Slite with optional filtering by owner. Use when you need to retrieve notes, optionally filtered by a specific user. Supports cursor-based pagination via the cursor parameter. | | `SLITE_SEARCH_GROUPS` | Search Groups | Tool to search for groups by name in Slite. Use when you need to find groups matching a search query. Supports cursor-based pagination via the cursor parameter. | | `SLITE_SEARCH_NOTES` | Search Notes | Tool to search notes based on a query with optional filters. Use when you need to find notes by search term, parent note, review state, or other criteria. Supports pagination and archived note inclusion. | | `SLITE_SEARCH_USERS` | Search Users | Tool to search for users in Slite by email, name, or username. Use when you need to find users in the organization. | | `SLITE_UPDATE_NOTE` | Update Note | Tool to update a note's content with markdown and/or title. Use when you need to modify an existing note's content or metadata. | | `SLITE_UPDATE_NOTE_ARCHIVED_STATE` | Update Note Archived State | Tool to update the archived state of a note in Slite. Use when you need to archive or unarchive a note. | | `SLITE_UPDATE_NOTE_OWNER` | Update Note Owner | Tool to update the owner of a note. Use when you need to transfer note ownership to a user or group. Either userId or groupId must be provided. | | `SLITE_UPDATE_TILE_IN_NOTE` | Update Tile in Note | Tool to update or create a tile within a Slite note with structured header and markdown content. Use when you need to update tile information including title, status, content, icon, or external URL. | | `SLITE_VERIFY_NOTE` | Verify Note | Tool to set a note's verification status to Verified with optional expiration. Use when you need to mark a note as verified or update its verification expiration date. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Slite MCP server is an implementation of the Model Context Protocol that connects your AI agent to Slite. It provides structured and secure access so your agent can perform Slite 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 Slite 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 Slite 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 Slite 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 Slite **What's happening:** - You create a Slite only session through Composio - Composio returns an MCP HTTP URL that exposes Slite tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["slite"]) 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=["slite"], ) 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 Slite through Composio's Tool Router. The agent can perform Slite 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 Slite MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/slite/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/slite/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/slite/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/slite/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/slite/framework/codex) - [OpenClaw](https://composio.dev/toolkits/slite/framework/openclaw) - [Hermes](https://composio.dev/toolkits/slite/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/slite/framework/cli) - [Google ADK](https://composio.dev/toolkits/slite/framework/google-adk) - [LangChain](https://composio.dev/toolkits/slite/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/slite/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/slite/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/slite/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. - [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices. - [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. - [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [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. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze. - [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization. - [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. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [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. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [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. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [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. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Slite MCP? With a standalone Slite MCP server, the agents and LLMs can only access a fixed set of Slite tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Slite 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 Slite tools. ### Can I manage the permissions and scopes for Slite while using Tool Router? Yes, absolutely. You can configure which Slite 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 Slite data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)