# How to integrate Uploadcare MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Uploadcare MCP with Vercel AI SDK v6", "toolkit": "Uploadcare", "toolkit_slug": "uploadcare", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/uploadcare/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/uploadcare/framework/ai-sdk.md", "updated_at": "2026-05-12T10:29:31.786Z" } ``` ## Introduction This guide walks you through connecting Uploadcare to Vercel AI SDK v6 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 Vercel AI 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 SDK](https://composio.dev/toolkits/uploadcare/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/uploadcare/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/uploadcare/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/uploadcare/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/uploadcare/framework/codex) - [OpenClaw](https://composio.dev/toolkits/uploadcare/framework/openclaw) - [Hermes](https://composio.dev/toolkits/uploadcare/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/uploadcare/framework/cli) - [Google ADK](https://composio.dev/toolkits/uploadcare/framework/google-adk) - [LangChain](https://composio.dev/toolkits/uploadcare/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/uploadcare/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/uploadcare/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/uploadcare/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Uploadcare integration - Using Composio's Tool Router to dynamically load and access Uploadcare tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## 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 | Tool slug | Name | Description | |---|---|---| | `UPLOADCARE_CHECK_AWS_REKOGNITION_MODERATION_STATUS` | Check AWS Rekognition Moderation Status | Tool to check the execution status of AWS Rekognition Moderation labels detection. Use after initiating a moderation check to monitor progress and determine when results are ready. | | `UPLOADCARE_CHECK_REMOVE_BG_STATUS` | Check Remove.bg Status | Tool to check Remove.bg execution status and get the UUID of the file with removed background. Use after requesting background removal to poll for completion and retrieve the processed file UUID. | | `UPLOADCARE_COPY_FILE_LOCAL` | Copy Uploadcare File to Local Storage | Tool to copy a file to local storage within the same Uploadcare project. Use when you need to create a duplicate of an existing file. | | `UPLOADCARE_CREATE_FILE_GROUP_UPLOAD` | Create File Group (Upload API) | Tool to create a file group from already uploaded files using Uploadcare's Upload API. Use after files have been uploaded to group them together. | | `UPLOADCARE_CREATE_WEBHOOK` | Create Uploadcare webhook | Create a new webhook subscription to receive notifications when file events occur. Use this to get real-time callbacks at your URL when files are uploaded, stored, deleted, or flagged. The project is automatically determined by your API credentials. Note: Each target_url must be unique per event type within your project. | | `UPLOADCARE_DELETE_FILE_METADATA_KEY` | Delete File Metadata Key | Tool to delete a specific metadata key from an Uploadcare file. Use when you need to remove obsolete metadata after file processing. | | `UPLOADCARE_DELETE_FILES` | Batch Delete Uploadcare Files | Tool to delete multiple files from Uploadcare storage in a single request. Use when you need to remove up to 100 files at once. Invalid UUIDs or missing files will be reported in the problems field. | | `UPLOADCARE_DELETE_GROUP` | Delete Uploadcare Group | Tool to delete a file group. Use when you need to remove a group from the project. Note that files within the group are not deleted, only the group itself. | | `UPLOADCARE_DELETE_SINGLE_FILE` | Delete Uploadcare File | Tool to delete a single file from Uploadcare storage by UUID. Use when you need to permanently remove a file from storage (note: file may remain in CDN cache). | | `UPLOADCARE_DELETE_WEBHOOK` | Delete Uploadcare Webhook | Permanently deletes a webhook subscription from your Uploadcare project. Use the List Webhooks action first to obtain the webhook ID. This action is irreversible. | | `UPLOADCARE_DELETE_WEBHOOK_BY_URL` | Delete Uploadcare Webhook by URL | Tool to delete a webhook subscription by its target URL. Use when you know the webhook's target URL but not its ID. | | `UPLOADCARE_EXECUTE_CLAMAV_SCAN` | Execute ClamAV virus scan | Tool to execute ClamAV virus scan on an uploaded file. Use this when you need to check if a file contains viruses or malware. The scan runs asynchronously - you receive a request_id to track the scan status. Results can be retrieved from file info or via webhooks. | | `UPLOADCARE_GET_AWS_REKOGNITION_EXECUTION_STATUS` | Get AWS Rekognition Execution Status | Tool to check AWS Rekognition execution status for label detection. Use after initiating an AWS Rekognition add-on execution to monitor job progress. | | `UPLOADCARE_GET_CLAMAV_SCAN_STATUS` | Get ClamAV Scan Status | Tool to check the execution status of a ClamAV virus scan. Use after initiating a ClamAV scan to monitor its progress and determine when results are available. | | `UPLOADCARE_GET_FILE_GROUP_INFO_UPLOAD` | Get File Group Info (Upload API) | Tool to get information about a file group from the Upload API. Use when you need to retrieve group details including file metadata from the upload endpoint. | | `UPLOADCARE_GET_FILE_INFO` | Get Uploadcare File Info | Tool to get information about a specific file. Use after uploading a file to retrieve detailed metadata and usage information. | | `UPLOADCARE_GET_FILE_METADATA` | Get File Metadata | Tool to retrieve all metadata key-value pairs associated with an Uploadcare file. Use when you need to inspect custom metadata attached to a file. | | `UPLOADCARE_GET_FILE_METADATA_KEY` | Get File Metadata Key Value | Tool to get the value of a specific metadata key for an Uploadcare file. Use when you need to retrieve custom metadata associated with a file. | | `UPLOADCARE_GET_GROUP_INFO` | Get Uploadcare Group Info | Tool to get information about a specific file group. Use when you need to retrieve detailed metadata about a group and its contained files. | | `UPLOADCARE_GET_PROJECT_INFO` | Get Uploadcare Project Info | Tool to get information about the current Uploadcare project. Use when you need to retrieve project configuration details. | | `UPLOADCARE_GET_UPLOADED_FILE_INFO` | Get Uploaded File Info | Tool to get information about an uploaded file using Uploadcare's Upload API. Use this to retrieve file metadata including size, MIME type, and content information immediately after upload. | | `UPLOADCARE_GET_URL_UPLOAD_STATUS` | Get URL Upload Status | Tool to check the status of a URL upload task. Use after initiating a file upload from a URL to monitor progress or verify completion. | | `UPLOADCARE_IMAGE_MIRROR` | Mirror Uploadcare Image | Tool to mirror an image horizontally via Uploadcare CDN. Use when you need the URL of a horizontally flipped image. | | `UPLOADCARE_LIST_FILES` | List Uploadcare Files | List files in an Uploadcare project with pagination and optional filtering. Use this tool to retrieve uploaded files. Supports filtering by storage status, removal status, and date range. Results are paginated with optional ordering. | | `UPLOADCARE_LIST_GROUPS` | List Uploadcare Groups | Tool to list groups in the project. Use when you need to retrieve paginated groups of files. | | `UPLOADCARE_LIST_WEBHOOKS` | List Uploadcare Webhooks | Retrieves all webhook subscriptions for the authenticated Uploadcare project. Use this tool to view configured webhooks that receive notifications for file events (uploads, deletions, storage, etc.). Returns an array of webhook objects with their IDs, target URLs, event types, and active status. | | `UPLOADCARE_ROTATE_IMAGE` | Rotate Image | Tool to rotate an image by specified degrees counterclockwise. Use when you need to rotate an uploaded image by 90, 180, or 270 degrees. Use after confirming the file UUID. | | `UPLOADCARE_START_MULTIPART_UPLOAD` | Start Multipart Upload | Tool to start a multipart upload session for files larger than 100MB. Use when you need to upload large files that exceed the direct upload size limit. Returns presigned URLs for uploading file parts. | | `UPLOADCARE_STORE_BATCH_FILES` | Batch Store Files | Tool to store multiple files in one request. Use when you need to mark up to 100 files as permanently stored in bulk. | | `UPLOADCARE_STORE_FILE` | Store Uploadcare File | Tool to mark an Uploadcare file as permanently stored. Use after uploading a file when you need to store it permanently. | | `UPLOADCARE_STORE_SINGLE_FILE` | Store Single Uploadcare File | Tool to store a single file by UUID permanently. Use when you need to make an uploaded file available permanently (stored files are retained indefinitely). | | `UPLOADCARE_UPDATE_FILE_METADATA_KEY` | Update File Metadata Key | Tool to update or set the value of a specific metadata key for a file. Use when you need to add or modify file metadata. | | `UPLOADCARE_UPDATE_WEBHOOK` | Update Uploadcare webhook | Update an existing webhook subscription by its ID. Use this to modify the target URL, event type, active status, or signing secret of a webhook. Only provide the fields you want to update - all fields are optional except the webhook ID. | | `UPLOADCARE_UPLOAD_FROM_URL` | Upload File from URL | Tool to upload a file from a publicly available URL to Uploadcare. Use when you need to import files from external URLs into your Uploadcare project. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Uploadcare MCP server is an implementation of the Model Context Protocol that connects your AI agent to Uploadcare. It provides structured and secure access so your agent can perform Uploadcare 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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 - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Uploadcare tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Uploadcare-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["uploadcare"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Uploadcare tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to uploadcare, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Uploadcare tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n๐Ÿ‘‹ Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["uploadcare"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to uploadcare, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n๐Ÿ‘‹ Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Uploadcare agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Uploadcare MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/uploadcare/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/uploadcare/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/uploadcare/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/uploadcare/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/uploadcare/framework/codex) - [OpenClaw](https://composio.dev/toolkits/uploadcare/framework/openclaw) - [Hermes](https://composio.dev/toolkits/uploadcare/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/uploadcare/framework/cli) - [Google ADK](https://composio.dev/toolkits/uploadcare/framework/google-adk) - [LangChain](https://composio.dev/toolkits/uploadcare/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/uploadcare/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/uploadcare/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/uploadcare/framework/crew-ai) ## Related Toolkits - [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices. - [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze. - [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization. - [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data. - [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease. - [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training. - [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses. - [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files. - [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently. - [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price. - [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere. - [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code. - [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more. - [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place. - [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work. - [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems. - [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project. - [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks. - [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API. - [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale. ## Frequently Asked Questions ### 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 Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)