# How to integrate Conveyor MCP with Google ADK ```json { "title": "How to integrate Conveyor MCP with Google ADK", "toolkit": "Conveyor", "toolkit_slug": "conveyor", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/conveyor/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/conveyor/framework/google-adk.md", "updated_at": "2026-05-06T08:07:22.514Z" } ``` ## Introduction This guide walks you through connecting Conveyor to Google ADK 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 Google ADK 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 - [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) - [Claude Code](https://composio.dev/toolkits/conveyor/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/conveyor/framework/claude-cowork) - [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) - [CLI](https://composio.dev/toolkits/conveyor/framework/cli) - [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) - [CrewAI](https://composio.dev/toolkits/conveyor/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Conveyor account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Conveyor - Build an agent that connects to Conveyor through MCP - Interact with Conveyor using natural language ## What is Google ADK? Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol. Key features include: - Gemini Integration: Native support for Google's Gemini models - MCP Toolset: Built-in support for Model Context Protocol tools - Streamable HTTP: Connect to external services through streamable HTTP - CLI and Web UI: Run agents via command line or web interface ## 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 | Tool to delete a folder by its ID. Use when you need to remove a specific folder after confirming its ID. | | `CONVEYOR_GENERATE_API_TOKEN` | Generate/Validate API Token Guidance | Tool to validate API token and provide guidance. Conveyor does not support API-based token creation; tokens must be created in the Conveyor UI. This action performs a real API call (using the provided metadata) to validate the existing API token and returns structured guidance. | | `CONVEYOR_GET_AUTHORIZATION_REQUEST` | Get Authorization Request | Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id. | | `CONVEYOR_GET_AUTHORIZATION_REQUESTS` | Get Authorization Requests | Tool to fetch authorization requests. Use when you need to list authorization requests, optionally filtered by status. | | `CONVEYOR_GET_AUTHORIZATIONS` | Get all authorization requests | Tool to retrieve all authorization requests. Use when you need to list all authorizations; optionally filter by status. Use after authenticating with a valid API token. | | `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 | Tool to retrieve all documents. Use after authenticating with a valid API key. | | `CONVEYOR_GET_FOLDERS` | Get all Conveyor folders | Tool to retrieve all folders. Use after authenticating with a valid API key to fetch the complete list of your Conveyor folders. | | `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 | Tool to retrieve knowledge base questions. Use when you need to fetch all questions from the Conveyor knowledge base. | | `CONVEYOR_GET_PRODUCT_LINES` | Get product lines | Tool to fetch all product lines. Use when you need to retrieve product lines after confirming API key validity. | | `CONVEYOR_PATCH_AUTHORIZATION` | Patch authorization | Tool to update or revoke an existing authorization. Use when managing authorization access groups or revoking access. | | `CONVEYOR_PATCH_DOCUMENT` | Patch Conveyor document | Tool to update document attributes. Use when you need to modify fields of an existing document by its ID. | | `CONVEYOR_POST_AUTHORIZATION` | Create new authorization | Tool to create a new authorization. Use when you need to grant access by email or from a prior authorization request. | | `CONVEYOR_POST_DOCUMENT` | Upload new document | Tool to upload a new document. Use when you have a local file (<=100MB) to send to Conveyor. | | `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_SINGLE_QUESTION` | Submit single question | Tool to submit a single question. Use when you need an immediate AI-generated answer for a specific product line question. | ## 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: - A Google API key for Gemini models - A Composio account and API key - Python 3.9 or later installed - Basic familiarity with Python ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key. - Copy the key and keep it safe. You will put this in GOOGLE_API_KEY. Composio API Key and User ID - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY. - Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Conveyor via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables Save all your credentials in the .env file. What's happening: - GOOGLE_API_KEY authenticates with Google's Gemini models - COMPOSIO_API_KEY authenticates with Composio - COMPOSIO_USER_ID identifies the user for session management ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate environment What's happening: - os reads environment variables - Composio is the main Composio SDK client - GoogleProvider declares that you are using Google ADK as the agent runtime - Agent is the Google ADK LLM agent class - McpToolset lets the ADK agent call MCP tools over HTTP ```python import os import warnings from composio import Composio from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") 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.") ``` ### 6. Create Composio client and Tool Router session What's happening: - Authenticates to Composio with your API key - Declares Google ADK as the provider - Spins up a short-lived MCP endpoint for your user and selected toolkit - Stores the MCP HTTP URL for the ADK MCP integration ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["conveyor"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent What's happening: - Connects the ADK agent to the Composio MCP endpoint through McpToolset - Uses Gemini as the model powering the agent - Lists exact tool names in instruction to reduce misnamed tool calls ```python composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Conveyor operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening: - adk run runs the agent in CLI mode - adk web . opens a web UI for interactive testing ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```python import os import warnings from composio import Composio from composio_google import GoogleProvider from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") 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.") composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider()) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["conveyor"], ) COMPOSIO_MCP_URL = composio_session.mcp.url composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Conveyor operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Conveyor with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Conveyor using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Conveyor tools - Environment variables keep your credentials secure and separate from code - Clear agent instructions reduce tool calling errors - The ADK web UI provides an interactive interface for testing and development You can extend this setup by adding more toolkits to the toolkits array in your session configuration. ## How to build Conveyor MCP Agent with another framework - [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) - [Claude Code](https://composio.dev/toolkits/conveyor/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/conveyor/framework/claude-cowork) - [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) - [CLI](https://composio.dev/toolkits/conveyor/framework/cli) - [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) - [CrewAI](https://composio.dev/toolkits/conveyor/framework/crew-ai) ## Related Toolkits - [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. - [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. - [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. - [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. - [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration. - [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease. - [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease. - [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services. - [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows. - [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses. - [Hyperbrowser](https://composio.dev/toolkits/hyperbrowser) - Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale. - [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals. - [Leverly](https://composio.dev/toolkits/leverly) - Leverly is a workflow automation platform that connects and coordinates actions across your apps. It streamlines repetitive processes so your business runs smoother, faster, and with fewer manual steps. - [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination. - [Make](https://composio.dev/toolkits/make) - Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code. - [Ntfy](https://composio.dev/toolkits/ntfy) - Ntfy is a notification service to send push messages to phones or desktops. Instantly deliver alerts and updates to users, devices, or teams. - [Persona](https://composio.dev/toolkits/persona) - Persona offers identity infrastructure to automate user verification and compliance. It helps organizations securely verify users and reduce fraud risk. ## 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 Google ADK? Yes, you can. Google ADK 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)