SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Conveyor MCP with Google ADK

Connect Google ADK to Conveyor MCP. List all pending authorization requests, fetch all documents in your trust center, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Conveyor logoConveyor
Api Key

Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.

25 Tools

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 submit security questionnaires, upload Trust Center documents, manage access authorizations, browse knowledge base questions, and track interactions 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

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKCodexOpenClawHermesAtomic AgentLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
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
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio 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.
  • 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.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

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
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

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
6

Import modules and validate environment

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.")
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
7

Create Composio client and Tool Router session

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}")
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
8

Set up the McpToolset and create the Agent

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 ;)")
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
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

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

Complete Code

Here's the complete code to get you started with Conveyor and Google ADK:

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.

TOOLS

Supported Tools

Every Conveyor action and event your agent gets out of the box.

Delete a Conveyor document

Tool to delete a specific document.

Delete folder

Permanently deletes a folder from the Conveyor Exchange by its UUID.

Get all access groups

Tool to retrieve all access groups for a program.

Get Authorization Request

Retrieves details of a specific authorization request from Conveyor Exchange by its ID.

Get Authorization Requests

Retrieves authorization requests from Conveyor's Trust Center.

Get authorizations

Retrieve authorizations from your Conveyor Trust Center.

Get all Conveyor connections

Retrieve a page of Conveyor connections, optionally filtered by domain.

Get all Conveyor documents

Retrieve documents and their metadata from the Conveyor Trust Center without request parameters.

List all Exchange folders

Retrieve folders from the Conveyor Exchange workspace, including IDs, names, and available timestamps and document IDs.

Get all interactions

Retrieve a page of document or Q&A interactions across Conveyor, optionally filtered by interaction type.

Get interactions by connection ID

Retrieve a page of interactions associated with a specific connection, optionally filtered by interaction type.

Get interactions by document ID

Retrieve a page of interactions associated with a specific document, optionally filtered by creation date.

Get Knowledge Base Questions

Retrieves knowledge base questions from Conveyor.

Get product lines

Retrieves all product lines configured in Conveyor.

Get questionnaires

Retrieves a page of Conveyor questionnaires with optional status, product line, and date filters.

Patch authorization

Update an existing authorization by revoking Trust Center access or changing its Access Group assignments.

Update Conveyor document

Update a Conveyor document's metadata.

Update questionnaire request

Updates a Conveyor questionnaire request by ID, including its external ID, case IDs, raw data, source system information, or file string.

Create new authorization

Tool to create a new authorization in Conveyor Exchange.

Upload new document

Tool to upload a new document to Conveyor's Knowledge Library.

Create new folder

Tool to create a new folder in Conveyor Exchange.

Submit new questionnaire

Tool to submit a new questionnaire to Conveyor.

Create questionnaire request

Tool to create a new questionnaire request in Conveyor.

Create new review

Tool to create a review in Conveyor with optional references to external VM unique IDs.

Submit single question

Submit a single question to Conveyor's AI knowledge base and receive an immediate answer.

FRAMEWORKS

How to build Conveyor MCP Agent with another framework

Claude Code logo

Claude Code

Use Conveyor MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Conveyor MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Conveyor MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Conveyor MCP with Claude Agent SDK

Codex logo

Codex

Use Conveyor MCP with Codex

OpenClaw logo

OpenClaw

Use Conveyor MCP with OpenClaw

Hermes logo

Hermes

Use Conveyor MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Conveyor MCP with Atomic Agent

LangChain logo

LangChain

Use Conveyor MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Conveyor MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Conveyor MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Conveyor MCP with LlamaIndex

CrewAI logo

CrewAI

Use Conveyor MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Conveyor MCP with Pydantic AI

AutoGen logo

AutoGen

Use Conveyor MCP with AutoGen

FAQ

Frequently asked questions

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.

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.

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.

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.

Start with Conveyor.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Conveyor tool your agent needs.Free to start.

Start building