# How to integrate Conveyor MCP with CrewAI ```json { "title": "How to integrate Conveyor MCP with CrewAI", "toolkit": "Conveyor", "toolkit_slug": "conveyor", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/conveyor/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/conveyor/framework/crew-ai.md", "updated_at": "2026-10-12T14:00:19.145Z" } ``` ## Introduction This guide walks you through connecting Conveyor to CrewAI using the Composio tool router. By the end, you'll have a working Conveyor agent that can list all pending authorization requests, fetch all documents in your trust center, delete a folder by its id through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Conveyor account through Composio's Conveyor MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Conveyor with - [Claude Code](https://composio.dev/toolkits/conveyor/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/conveyor/framework/claude-cowork) - [OpenAI Agents SDK](https://composio.dev/toolkits/conveyor/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/conveyor/framework/claude-agents-sdk) - [Codex](https://composio.dev/toolkits/conveyor/framework/codex) - [OpenClaw](https://composio.dev/toolkits/conveyor/framework/openclaw) - [Hermes](https://composio.dev/toolkits/conveyor/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/conveyor/framework/atomic-agent) - [Google ADK](https://composio.dev/toolkits/conveyor/framework/google-adk) - [LangChain](https://composio.dev/toolkits/conveyor/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/conveyor/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/conveyor/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/conveyor/framework/llama-index) - [Pydantic AI](https://composio.dev/toolkits/conveyor/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/conveyor/framework/autogen) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Conveyor connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Conveyor - Build a conversational loop where your agent can execute Conveyor 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 Conveyor MCP server, and what's possible with it? The Conveyor MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Conveyor account. It provides structured and secure access to your security reviews and compliance workflows, so your agent can perform actions like retrieving documents, managing authorization requests, tracking connections, and automating security questionnaire processes on your behalf. - Authorization request management: Fetch, list, and review details of all authorization requests, making it easy for your agent to help you track and respond to security and compliance requests in real time. - Document and folder automation: Retrieve, organize, or delete specific documents and folders, ensuring your Trust Center stays tidy and up to date without manual effort. - Connection insights and tracking: Access a complete list of your Conveyor connections, letting your agent monitor integrations and stay on top of your security ecosystem. - Interaction history by document: Instantly pull all interactions related to a specific document, so your agent can summarize or audit user activity for compliance needs. - API token validation and guidance: Use AI-driven guidance to validate API tokens and get structured support for access issues, helping keep your Conveyor integration secure and running smoothly. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `CONVEYOR_DELETE_DOCUMENT` | Delete a Conveyor document | Tool to delete a specific document. Use when you need to remove a document by its ID. | | `CONVEYOR_DELETE_FOLDER` | Delete folder | Permanently deletes a folder from the Conveyor Exchange by its UUID. Use GET_FOLDERS first to retrieve the folder_id. This action is irreversible. | | `CONVEYOR_GET_ACCESS_GROUPS` | Get all access groups | Tool to retrieve all access groups for a program. Use when you need to fetch the complete list of access groups configured in the Conveyor Exchange. | | `CONVEYOR_GET_AUTHORIZATION_REQUEST` | Get Authorization Request | Retrieves details of a specific authorization request from Conveyor Exchange by its ID. Use this to get information about a pending or processed access request, including the requestor's email, message, status, and associated dataroom. | | `CONVEYOR_GET_AUTHORIZATION_REQUESTS` | Get Authorization Requests | Retrieves authorization requests from Conveyor's Trust Center. Use this tool to: - List all authorization requests (no filters) - Get pending requests awaiting approval (status='requested') - Filter by specific status ('initial', 'requested', 'approved', 'ignored') - Filter by requester email address Returns a list of authorization requests with details including requester email, status, timestamps, and optional CRM links. | | `CONVEYOR_GET_AUTHORIZATIONS` | Get authorizations | Retrieve authorizations from your Conveyor Trust Center. Authorizations control who has access to view documents. Use this to list all authorizations or filter by status ('gated', 'authorized', 'revoked') or email address. Requires a valid API token for authentication. | | `CONVEYOR_GET_CONNECTIONS` | Get all Conveyor connections | Tool to retrieve all connections. Use when you need to fetch the complete list of your Conveyor connections. Use after authenticating with a valid API key. | | `CONVEYOR_GET_DOCUMENTS` | Get all Conveyor documents | Retrieves all documents from the Conveyor trust center. Returns a list of documents with their metadata including name, description, access level, versions, and timestamps. No parameters required - simply call to get all documents. | | `CONVEYOR_GET_FOLDERS` | List all Exchange folders | Retrieves all folders from the Conveyor Exchange workspace. Returns a list of folders with their IDs, names, timestamps, and associated document IDs. Use this to discover available folders before uploading documents or managing folder contents. | | `CONVEYOR_GET_INTERACTIONS` | Get all interactions | Tool to get all interactions (document interactions, q&a interactions) with optional filters. Use when you need to retrieve and filter interactions across all documents and Q&A sessions. | | `CONVEYOR_GET_INTERACTIONS_BY_CONNECTION_ID` | Get interactions by connection ID | Tool to fetch interactions associated with a specific connection. Use when you need to list all interactions for a given connection after validating its existence. | | `CONVEYOR_GET_INTERACTIONS_BY_DOCUMENT_ID` | Get interactions by document ID | Tool to fetch interactions associated with a specific document. Use when you need to list all interactions for a given document after validating its existence. | | `CONVEYOR_GET_KNOWLEDGE_BASE_QUESTIONS` | Get Knowledge Base Questions | Retrieves knowledge base questions from Conveyor. Use to list, search, or paginate through Q&A entries stored in the knowledge base for compliance and security questionnaires. | | `CONVEYOR_GET_PRODUCT_LINES` | Get product lines | Retrieves all product lines configured in Conveyor. Use this action to list available product lines for organizing trust documentation, authorizations, and security reviews by business segment. This is a read-only operation that requires a valid API token. Returns a list of product lines with their IDs, names, and descriptions. The list may be empty if no product lines have been configured. | | `CONVEYOR_GET_QUESTIONNAIRES` | Get questionnaires | Retrieves all questionnaires from Conveyor with optional filters. Use this to list questionnaires by status, product line, or date ranges. Returns questionnaire metadata including assignee, connection, product lines, and completion status. | | `CONVEYOR_PATCH_AUTHORIZATION` | Patch authorization | Update an existing authorization by revoking access or modifying Access Group assignments. Use this tool to: - Revoke a user's access to the Trust Center (set revoke=true) - Update which Access Groups a user belongs to (provide access_group_ids list) At least one of 'revoke' or 'access_group_ids' must be provided. | | `CONVEYOR_PATCH_DOCUMENT` | Update Conveyor document | Update a Conveyor document's metadata. Use this to change a document's name, description, access level, folder location, or other properties. Requires the document UUID. | | `CONVEYOR_PATCH_QUESTIONNAIRE_REQUEST` | Update questionnaire request | Tool to update a questionnaire request in Conveyor. Use this to modify an existing questionnaire request's external ID, case IDs, raw data, or source system information. | | `CONVEYOR_POST_AUTHORIZATION` | Create new authorization | Tool to create a new authorization in Conveyor Exchange. Use this to grant access to a user by email address or by approving an existing authorization request. Provide either 'email' (to create a new authorization for that email) or 'request_id' (to approve an existing authorization request), but not both. | | `CONVEYOR_POST_DOCUMENT` | Upload new document | Tool to upload a new document to Conveyor's Knowledge Library. Use when you need to add a file (<=100MB) for security compliance documentation. | | `CONVEYOR_POST_FOLDER` | Create new folder | Tool to create a new folder in Conveyor Exchange. Use when you need to organize items into folders programmatically after obtaining an API key. | | `CONVEYOR_POST_QUESTIONNAIRE` | Submit new questionnaire | Tool to submit a new questionnaire to Conveyor. Use when you need to create a security questionnaire or RFP submission with file uploads, portal links, or Salesforce integration. | | `CONVEYOR_POST_QUESTIONNAIRE_REQUEST` | Create questionnaire request | Tool to create a new questionnaire request in Conveyor. Use when you need to submit a security questionnaire or compliance request for processing. Requires submitter_email and either external_id with raw_data OR case_ids from Salesforce. | | `CONVEYOR_POST_REVIEW` | Create new review | Tool to create a review in Conveyor with optional references to external VM unique IDs. Use when you need to create a vendor review programmatically. | | `CONVEYOR_POST_SINGLE_QUESTION` | Submit single question | Submit a single question to Conveyor's AI knowledge base and receive an immediate answer. Use this when responding to security questionnaires, compliance inquiries, or knowledge base queries. Returns the AI-generated answer along with confidence scoring when available. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Conveyor MCP server is an implementation of the Model Context Protocol that connects your AI agent to Conveyor. It provides structured and secure access so your agent can perform Conveyor 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 Conveyor 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 Conveyor 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 Conveyor 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 Conveyor **What's happening:** - You create a Conveyor only session through Composio - Composio returns an MCP HTTP URL that exposes Conveyor tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["conveyor"]) 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=["conveyor"], ) 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 Conveyor through Composio's Tool Router. The agent can perform Conveyor 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 Conveyor MCP Agent with another framework - [Claude Code](https://composio.dev/toolkits/conveyor/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/conveyor/framework/claude-cowork) - [OpenAI Agents SDK](https://composio.dev/toolkits/conveyor/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/conveyor/framework/claude-agents-sdk) - [Codex](https://composio.dev/toolkits/conveyor/framework/codex) - [OpenClaw](https://composio.dev/toolkits/conveyor/framework/openclaw) - [Hermes](https://composio.dev/toolkits/conveyor/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/conveyor/framework/atomic-agent) - [Google ADK](https://composio.dev/toolkits/conveyor/framework/google-adk) - [LangChain](https://composio.dev/toolkits/conveyor/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/conveyor/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/conveyor/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/conveyor/framework/llama-index) - [Pydantic AI](https://composio.dev/toolkits/conveyor/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/conveyor/framework/autogen) ## Related Toolkits - [0CodeKit](https://composio.dev/toolkits/0codekit) - 0CodeKit is a utility API platform for AI, document, image, and data workflows. Use it to convert, validate, generate, store, and automate data without custom backend code. - [Airtop](https://composio.dev/toolkits/airtop) - Airtop is a cloud browser platform for AI-powered web automation. Use it to navigate sites, extract data, and run reusable browser workflows. - [Apify MCP](https://composio.dev/toolkits/apify_mcp) - Apify MCP is the official MCP server for Apify's web scraping and browser automation platform. Use it to run actors, collect structured web data, and automate crawling workflows. - [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations. - [Basin](https://composio.dev/toolkits/basin) - Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code. - [Bika.ai](https://composio.dev/toolkits/bika) - Bika.ai is an AI automation database platform for managing spaces, teams, records, automations, and outgoing webhooks. It helps teams organize structured data and automate database-driven workflows in one place. - [Botster](https://composio.dev/toolkits/botster) - Botster is a web automation service for running configurable data collection bots. Use it to collect structured web data without building and maintaining scrapers yourself. - [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications. - [BrowserAct](https://composio.dev/toolkits/browseract) - BrowserAct is a hosted browser-automation service for running web workflows. Use it to execute repeatable browser tasks with templates, proxies, and APIs. - [Celigo](https://composio.dev/toolkits/celigo) - Celigo is an integration platform as a service for connecting apps, data, and business workflows. It helps teams automate cross-system processes without building every integration from scratch. - [CheckFlow](https://composio.dev/toolkits/checkflow) - CheckFlow is a workflow and checklist platform for repeatable processes, tasks, templates, teams, data sets, and automation. Use it to standardize operations, track process execution, and keep teams aligned. - [CrewAI](https://composio.dev/toolkits/crew_ai) - CrewAI is a platform for running deployed automations and managing AMP control-plane resources. Use it to automate workflows and centrally control SaaS automation resources. - [Cronfree Time Scheduler](https://composio.dev/toolkits/cronfree_time_scheduler) - Cronfree Time Scheduler is an API-based scheduler for recurring webhook calls. Use it to create and remove timezone-aware schedules without running cron. - [Crowdin](https://composio.dev/toolkits/crowdin) - Crowdin is a localization management platform that streamlines translation workflows and collaboration. It helps teams centralize multilingual content, boost productivity, and automate translation processes. - [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights. - [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way. - [Dify](https://composio.dev/toolkits/dify) - Dify is a platform for running and managing published workflow apps via a Service API. Use it to execute workflows and inspect configuration and run history quickly. - [Digital Humani](https://composio.dev/toolkits/digital_humani) - Digital Humani is a reforestation API for browsing planting projects, submitting tree requests, and tracking planted trees. It helps teams connect climate action directly to products, campaigns, and customer experiences. - [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease. - [EnforcedFlow](https://composio.dev/toolkits/enforcedflow) - EnforcedFlow is a work routing platform for advanced round-robin groups, agent criteria, availability, and email assignments. It helps teams distribute work fairly and quickly using configurable assignment rules. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Conveyor MCP? With a standalone Conveyor MCP server, the agents and LLMs can only access a fixed set of Conveyor tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Conveyor 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 Conveyor tools. ### Can I manage the permissions and scopes for Conveyor while using Tool Router? Yes, absolutely. You can configure which Conveyor 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 Conveyor data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)