# How to integrate Slite MCP with Autogen ```json { "title": "How to integrate Slite MCP with Autogen", "toolkit": "Slite", "toolkit_slug": "slite", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/slite/framework/autogen", "markdown_url": "https://composio.dev/toolkits/slite/framework/autogen.md", "updated_at": "2026-03-29T06:50:56.164Z" } ``` ## Introduction This guide walks you through connecting Slite to AutoGen 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 AutoGen 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) - [CrewAI](https://composio.dev/toolkits/slite/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Slite - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Slite tools - Run a live chat loop where you ask the agent to perform Slite operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## 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 agents and assistants directly to Slite. Instead of manually wiring Slite APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. 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 You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Slite account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 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 Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Slite via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Slite connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Slite tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Slite session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["slite"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Slite tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Slite assistant agent with MCP tools agent = AssistantAgent( name="slite_assistant", description="An AI assistant that helps with Slite operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Slite tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Slite related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Slite session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["slite"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Slite assistant agent with MCP tools agent = AssistantAgent( name="slite_assistant", description="An AI assistant that helps with Slite operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Slite related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Slite through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Slite, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## 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) - [CrewAI](https://composio.dev/toolkits/slite/framework/crew-ai) ## 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 Autogen? Yes, you can. Autogen 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)