How to integrate Google cloud vision MCP with OpenAI Agents SDK

Framework Integration Gradient
Google cloud vision Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Google cloud vision to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Google cloud vision agent that can bulk import product images from gcs csv, list all vision ai service locations, create a new product for image recognition, delete an outdated product and its images through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Google cloud vision account through Composio's Google cloud vision MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Google cloud vision
  • Configure an AI agent that can use Google cloud vision as a tool
  • Run a live chat session where you can ask the agent to perform Google cloud vision operations

What is open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

What is the Google cloud vision MCP server, and what's possible with it?

The Google cloud vision MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Cloud Vision account. It provides structured and secure access to your image analysis resources, so your agent can perform actions like registering products, managing reference images, listing endpoints, and automating large-scale image operations on your behalf.

  • Product and reference image management: Easily create new products and add reference images for visual search, enabling your agent to organize and expand your vision datasets effortlessly.
  • Bulk import and product set operations: Let your agent import large numbers of reference images into product sets from Cloud Storage CSV files, streamlining dataset curation at scale.
  • Automated product cleanup and deletion: Direct your agent to purge unused or orphan products from your project, keeping your cloud resources tidy without manual effort.
  • Location and endpoint discovery: Quickly list available Vision AI service locations and existing IndexEndpoints, making it easy for your agent to select optimal regions and manage deployment targets.
  • Vision API operation tracking: Retrieve and review ongoing or past Vision API operations, so your agent can monitor processing jobs and ensure workflow transparency.

Supported Tools & Triggers

Tools
Create Vision ProductTool to create and return a new Product resource.
Create ReferenceImageTool to create a ReferenceImage under a product.
Delete ProductTool to permanently delete a Product and its reference images.
Get ProductTool to get information associated with a Product.
Get Product SetTool to get a ProductSet.
Import Product SetsTool to asynchronously import reference images into ProductSets from a CSV in GCS.
List IndexEndpointsTool to list IndexEndpoints in a project and location.
List LocationsTool to list available Vision AI service locations for a project.
List Vision API OperationsTool to list operations that match the specified filter.
Purge ProductsTool to asynchronously delete products in a ProductSet or orphan products.
Update ProductTool to update a Product's mutable fields: displayName, description, and productLabels.
Update Product SetTool to update a ProductSet resource.
Add Product to ProductSetTool to add a Product to a specified ProductSet.
Cancel Vision OperationTool to cancel a long-running Vision API operation.
Delete Vision API OperationTool to delete a long-running Vision API operation.
Delete Product SetTool to permanently delete a ProductSet.
Delete Reference ImageTool to permanently delete a reference image.
Get Vision API OperationTool to get the latest state of a long-running operation.
Get Reference ImageTool to get information associated with a ReferenceImage.
List Products in ProductSetTool to list Products in a specified ProductSet.
List ProjectsTool to list Google Cloud projects accessible by the authenticated user.
List Reference ImagesTool to list reference images for a product.
Remove Product from ProductSetTool to remove a Product from a specified ProductSet.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Google cloud vision project
  • Some knowledge of Python or Typescript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Google cloud vision.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Google cloud vision Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["google_cloud_vision"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only google_cloud_vision.
  • The router checks the user's Google cloud vision connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Google cloud vision.
  • This approach keeps things lightweight and lets the agent request Google cloud vision tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Google cloud vision. "
        "Help users perform Google cloud vision operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Google cloud vision and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Google cloud vision operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Google cloud vision.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Google cloud vision and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["google_cloud_vision"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Google cloud vision. "
        "Help users perform Google cloud vision operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Google cloud vision MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Google cloud vision.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Google cloud vision MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Google cloud vision MCP?

With a standalone Google cloud vision MCP server, the agents and LLMs can only access a fixed set of Google cloud vision tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google cloud vision and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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 Google cloud vision tools.

Can I manage the permissions and scopes for Google cloud vision while using Tool Router?

Yes, absolutely. You can configure which Google cloud vision 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 Google cloud vision data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.