How to integrate Uploadcare MCP with OpenAI Agents SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Uploadcare logo
OpenAI Agents SDK logo
divider

Introduction

This guide walks you through connecting Uploadcare to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Uploadcare agent that can list all uploaded files from last week, rotate image file by 90 degrees clockwise, get direct download link for specific file through natural language commands.

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

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

Also integrate Uploadcare with

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 Uploadcare
  • Configure an AI agent that can use Uploadcare as a tool
  • Run a live chat session where you can ask the agent to perform Uploadcare operations

What is OpenAI 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 Uploadcare MCP server, and what's possible with it?

The Uploadcare MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Uploadcare account. It provides structured and secure access to your file storage, processing, and delivery pipeline, so your agent can perform actions like listing files, retrieving file info, managing webhooks, rotating images, and handling file metadata on your behalf.

  • Comprehensive file listing and retrieval: Ask your agent to list all files stored in your Uploadcare project, filter by criteria, or fetch detailed metadata for any file.
  • Direct file download and sharing: Effortlessly generate secure, temporary download links for your files so you can share them or integrate with other services.
  • Automated image processing: Let your agent rotate images by 90, 180, or 270 degrees, making quick edits or transformations without manual intervention.
  • Webhook management for event automation: Easily create, list, or delete webhooks so your agent can subscribe to file events and enable real-time notifications or integrations.
  • Metadata and group management: Enable your agent to update or delete file metadata and organize files into groups for streamlined file handling and workflows.

Supported Tools & Triggers

Tools
Check AWS Rekognition Moderation StatusTool to check the execution status of AWS Rekognition Moderation labels detection.
Check Remove.bg StatusTool to check Remove.
Copy Uploadcare File to Local StorageTool to copy a file to local storage within the same Uploadcare project.
Create File Group (Upload API)Tool to create a file group from already uploaded files using Uploadcare's Upload API.
Create Uploadcare webhookCreate a new webhook subscription to receive notifications when file events occur.
Delete File Metadata KeyTool to delete a specific metadata key from an Uploadcare file.
Batch Delete Uploadcare FilesTool to delete multiple files from Uploadcare storage in a single request.
Delete Uploadcare GroupTool to delete a file group.
Delete Uploadcare FileTool to delete a single file from Uploadcare storage by UUID.
Delete Uploadcare WebhookPermanently deletes a webhook subscription from your Uploadcare project.
Delete Uploadcare Webhook by URLTool to delete a webhook subscription by its target URL.
Execute ClamAV virus scanTool to execute ClamAV virus scan on an uploaded file.
Get AWS Rekognition Execution StatusTool to check AWS Rekognition execution status for label detection.
Get ClamAV Scan StatusTool to check the execution status of a ClamAV virus scan.
Get File Group Info (Upload API)Tool to get information about a file group from the Upload API.
Get Uploadcare File InfoTool to get information about a specific file.
Get File MetadataTool to retrieve all metadata key-value pairs associated with an Uploadcare file.
Get File Metadata Key ValueTool to get the value of a specific metadata key for an Uploadcare file.
Get Uploadcare Group InfoTool to get information about a specific file group.
Get Uploadcare Project InfoTool to get information about the current Uploadcare project.
Get Uploaded File InfoTool to get information about an uploaded file using Uploadcare's Upload API.
Get URL Upload StatusTool to check the status of a URL upload task.
Mirror Uploadcare ImageTool to mirror an image horizontally via Uploadcare CDN.
List Uploadcare FilesList files in an Uploadcare project with pagination and optional filtering.
List Uploadcare GroupsTool to list groups in the project.
List Uploadcare WebhooksRetrieves all webhook subscriptions for the authenticated Uploadcare project.
Rotate ImageTool to rotate an image by specified degrees counterclockwise.
Start Multipart UploadTool to start a multipart upload session for files larger than 100MB.
Batch Store FilesTool to store multiple files in one request.
Store Uploadcare FileTool to mark an Uploadcare file as permanently stored.
Store Single Uploadcare FileTool to store a single file by UUID permanently.
Update File Metadata KeyTool to update or set the value of a specific metadata key for a file.
Update Uploadcare webhookUpdate an existing webhook subscription by its ID.
Upload File from URLTool to upload a file from a publicly available URL to Uploadcare.

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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Uploadcare 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 Uploadcare.

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 Uploadcare Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["uploadcare"]
)

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 uploadcare.
  • The router checks the user's Uploadcare connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Uploadcare.
  • This approach keeps things lightweight and lets the agent request Uploadcare 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 Uploadcare. "
        "Help users perform Uploadcare 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 Uploadcare 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 Uploadcare 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 Uploadcare.
  • 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 Uploadcare and OpenAI 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=["uploadcare"]
)
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 Uploadcare. "
        "Help users perform Uploadcare 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 Uploadcare MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Uploadcare.

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 Uploadcare MCP Agent with another framework

Claude Agent SDK logo

Claude Agent SDK

Use Uploadcare MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Uploadcare MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Uploadcare MCP with Claude Cowork

Codex logo

Codex

Use Uploadcare MCP with Codex

OpenClaw logo

OpenClaw

Use Uploadcare MCP with OpenClaw

Hermes logo

Hermes

Use Uploadcare MCP with Hermes

CLI logo

CLI

Use Uploadcare MCP with CLI

Google ADK logo

Google ADK

Use Uploadcare MCP with Google ADK

LangChain logo

LangChain

Use Uploadcare MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Uploadcare MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Uploadcare MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Uploadcare MCP with LlamaIndex

CrewAI logo

CrewAI

Use Uploadcare MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Uploadcare MCP?

With a standalone Uploadcare MCP server, the agents and LLMs can only access a fixed set of Uploadcare tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Uploadcare 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 Uploadcare tools.

Can I manage the permissions and scopes for Uploadcare while using Tool Router?

Yes, absolutely. You can configure which Uploadcare 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 Uploadcare 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.

Get started for freeGet a demo↗