How to integrate Uploadcare MCP with Claude Agent SDK

This guide walks you through connecting Uploadcare to the Claude Agent 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 Claude Agent 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.

Get started for freeGet a demo
Uploadcare logoUploadcare
Api Key

Uploadcare is a file handling platform for uploading, storing, and delivering files at scale. It streamlines file management, processing, and delivery for web and mobile apps.

34 Tools

Introduction

This guide walks you through connecting Uploadcare to the Claude Agent 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 Claude Agent 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

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic 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 Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Uploadcare account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Uploadcare functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Uploadcare
  const session = await composio.create(USER_ID, {
    toolkits: ['uploadcare'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Uploadcare
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Uploadcare tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Uploadcare
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Uploadcare and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['uploadcare']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Uploadcare tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Uploadcare through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Check AWS Rekognition Moderation Status

Tool to check the execution status of AWS Rekognition Moderation labels detection.

Check Remove.bg Status

Tool to check Remove.

Copy Uploadcare File to Local Storage

Tool 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 webhook

Create a new webhook subscription to receive notifications when file events occur.

Delete File Metadata Key

Tool to delete a specific metadata key from an Uploadcare file.

Batch Delete Uploadcare Files

Tool to delete multiple files from Uploadcare storage in a single request.

Delete Uploadcare Group

Tool to delete a file group.

Delete Uploadcare File

Tool to delete a single file from Uploadcare storage by UUID.

Delete Uploadcare Webhook

Permanently deletes a webhook subscription from your Uploadcare project.

Delete Uploadcare Webhook by URL

Tool to delete a webhook subscription by its target URL.

Execute ClamAV virus scan

Tool to execute ClamAV virus scan on an uploaded file.

Get AWS Rekognition Execution Status

Tool to check AWS Rekognition execution status for label detection.

Get ClamAV Scan Status

Tool 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 Info

Tool to get information about a specific file.

Get File Metadata

Tool to retrieve all metadata key-value pairs associated with an Uploadcare file.

Get File Metadata Key Value

Tool to get the value of a specific metadata key for an Uploadcare file.

Get Uploadcare Group Info

Tool to get information about a specific file group.

Get Uploadcare Project Info

Tool to get information about the current Uploadcare project.

Get Uploaded File Info

Tool to get information about an uploaded file using Uploadcare's Upload API.

Get URL Upload Status

Tool to check the status of a URL upload task.

Mirror Uploadcare Image

Tool to mirror an image horizontally via Uploadcare CDN.

List Uploadcare Files

List files in an Uploadcare project with pagination and optional filtering.

List Uploadcare Groups

Tool to list groups in the project.

List Uploadcare Webhooks

Retrieves all webhook subscriptions for the authenticated Uploadcare project.

Rotate Image

Tool to rotate an image by specified degrees counterclockwise.

Start Multipart Upload

Tool to start a multipart upload session for files larger than 100MB.

Batch Store Files

Tool to store multiple files in one request.

Store Uploadcare File

Tool to mark an Uploadcare file as permanently stored.

Store Single Uploadcare File

Tool to store a single file by UUID permanently.

Update File Metadata Key

Tool to update or set the value of a specific metadata key for a file.

Update Uploadcare webhook

Update an existing webhook subscription by its ID.

Upload File from URL

Tool to upload a file from a publicly available URL to Uploadcare.

FRAMEWORKS

How to build Uploadcare MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Uploadcare MCP with OpenAI Agents 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

Frequently asked questions

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.

Yes, you can. Claude Agent 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.

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.

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.

Start with Uploadcare.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies