# How to integrate Cloudconvert MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Cloudconvert MCP with Vercel AI SDK v6", "toolkit": "Cloudconvert", "toolkit_slug": "cloudconvert", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/cloudconvert/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/cloudconvert/framework/ai-sdk.md", "updated_at": "2026-05-12T10:06:38.656Z" } ``` ## Introduction This guide walks you through connecting Cloudconvert to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Cloudconvert agent that can convert a pdf to word document format, export a converted file directly to s3, list all supported video conversion formats through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Cloudconvert account through Composio's Cloudconvert MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Cloudconvert with - [OpenAI Agents SDK](https://composio.dev/toolkits/cloudconvert/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/cloudconvert/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/cloudconvert/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/cloudconvert/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/cloudconvert/framework/codex) - [OpenClaw](https://composio.dev/toolkits/cloudconvert/framework/openclaw) - [Hermes](https://composio.dev/toolkits/cloudconvert/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/cloudconvert/framework/cli) - [Google ADK](https://composio.dev/toolkits/cloudconvert/framework/google-adk) - [LangChain](https://composio.dev/toolkits/cloudconvert/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/cloudconvert/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/cloudconvert/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/cloudconvert/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Cloudconvert integration - Using Composio's Tool Router to dynamically load and access Cloudconvert 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 Cloudconvert MCP server, and what's possible with it? The Cloudconvert MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your CloudConvert account. It provides structured and secure access to your file conversion workflows, so your agent can perform actions like converting files, exporting results to cloud storage, managing webhooks, and exploring supported formats on your behalf. - Seamless file conversion: Ask your agent to convert documents, images, audio, video, spreadsheets, or presentations between hundreds of supported formats automatically. - Automated export to cloud storage: Direct your agent to export converted files directly into your Google Cloud Storage or Amazon S3 buckets, streamlining storage and distribution. - Format discovery and optimization: Have the agent list all supported conversion formats, engines, and options, so you can choose the best settings for your needs. - Webhook management: Let your agent create, list, or delete webhooks to receive real-time notifications about conversion events and automate downstream processes. - Task tracking and user info: Retrieve detailed task histories, filter by status or date, and confirm the authenticated user’s account details for secure operations. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `CLOUDCONVERT_CREATE_EXPORT_GOOGLE_CLOUD_STORAGE_TASK` | Create Export Google Cloud Storage Task | Tool to create a task to export files to a Google Cloud Storage bucket. Use after conversion when you need to store results directly into GCS. Ensure service account credentials have the proper permissions. | | `CLOUDCONVERT_CREATE_EXPORT_S3_TASK` | Create Export S3 Task | Tool to create a task to export files to an Amazon S3 bucket. Use after conversion when you need to store results directly into S3. Ensure AWS credentials have s3:PutObject (and PutObjectAcl if using non-default ACL) permissions. | | `CLOUDCONVERT_CREATE_WEBHOOK` | Create Webhook | Creates a new webhook to receive CloudConvert event notifications. Use this when you need to be notified about job status changes (created, finished, or failed) via HTTP POST requests to your server. | | `CLOUDCONVERT_DELETE_WEBHOOK` | Delete Webhook | Permanently delete a webhook by its ID. Use this when you no longer need to receive event notifications for a specific webhook. The webhook ID can be obtained from the create_webhook or list_webhooks actions. | | `CLOUDCONVERT_LIST_OPERATIONS` | List Operations | Tool to list all possible CloudConvert operations with their available options and engine details. Use when you need to discover what operations are available, check operation requirements, or filter by input/output formats before creating tasks. | | `CLOUDCONVERT_LIST_SUPPORTED_FORMATS` | List Supported Formats | Tool to list all supported conversion formats, engines, and options. Use when you need to discover available conversions before creating tasks. | | `CLOUDCONVERT_LIST_TASKS` | List Tasks | List all CloudConvert tasks with their status, payload and results. Use this tool to: - Monitor conversion task progress and status - Find tasks by status (waiting, processing, finished, error) - Filter tasks by job ID to see all tasks in a specific job - Retrieve task results and output file URLs - Debug failed conversions by checking error codes and messages Tasks are automatically deleted 24 hours after completion. | | `CLOUDCONVERT_LIST_WEBHOOKS` | List Webhooks | Tool to list all webhooks. Use when you need to retrieve existing webhooks before managing or inspecting them. | | `CLOUDCONVERT_SHOW_USER` | Show User | Retrieves the current authenticated user's CloudConvert account information. Returns the user's ID, username, email, remaining conversion credits, and account creation date. Requires the 'user.read' scope. Useful for verifying authentication and checking available credits. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Cloudconvert MCP server is an implementation of the Model Context Protocol that connects your AI agent to Cloudconvert. It provides structured and secure access so your agent can perform Cloudconvert 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 Cloudconvert 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 Cloudconvert-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: ["cloudconvert"], }); 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 Cloudconvert 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 cloudconvert, 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 Cloudconvert 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: ["cloudconvert"], }); 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 cloudconvert, 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 Cloudconvert 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 Cloudconvert MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/cloudconvert/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/cloudconvert/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/cloudconvert/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/cloudconvert/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/cloudconvert/framework/codex) - [OpenClaw](https://composio.dev/toolkits/cloudconvert/framework/openclaw) - [Hermes](https://composio.dev/toolkits/cloudconvert/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/cloudconvert/framework/cli) - [Google ADK](https://composio.dev/toolkits/cloudconvert/framework/google-adk) - [LangChain](https://composio.dev/toolkits/cloudconvert/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/cloudconvert/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/cloudconvert/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/cloudconvert/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. - [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. - [Docmosis](https://composio.dev/toolkits/docmosis) - Docmosis generates PDF and Word documents from user-defined templates. It's perfect for merging data fields to quickly produce reports, invoices, and business letters. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Cloudconvert MCP? With a standalone Cloudconvert MCP server, the agents and LLMs can only access a fixed set of Cloudconvert tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Cloudconvert 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 Cloudconvert tools. ### Can I manage the permissions and scopes for Cloudconvert while using Tool Router? Yes, absolutely. You can configure which Cloudconvert 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 Cloudconvert data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)