# How to integrate Cloudconvert MCP with Claude Code ```json { "title": "How to integrate Cloudconvert MCP with Claude Code", "toolkit": "Cloudconvert", "toolkit_slug": "cloudconvert", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/cloudconvert/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/cloudconvert/framework/claude-code.md", "updated_at": "2026-05-12T10:06:38.656Z" } ``` ## Introduction Manage your Cloudconvert directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## 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 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) - [Vercel AI SDK](https://composio.dev/toolkits/cloudconvert/framework/ai-sdk) - [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 - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Cloudconvert to Claude Code ### Connecting Cloudconvert to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## 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 Claude Code (and other AI assistants like Claude and Cursor) directly to your Cloudconvert account. It provides structured and secure access so Claude can perform Cloudconvert operations on your behalf. 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 starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Cloudconvert account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["cloudconvert"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http cloudconvert-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; 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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['cloudconvert'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http cloudconvert-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Cloudconvert MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (cloudconvert-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http cloudconvert-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Cloudconvert MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your cloudconvert-composio entry in the list - This confirms that Claude Code can now access Cloudconvert tools If everything is wired up, you should see your cloudconvert-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Cloudconvert The first time you try to use Cloudconvert tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Cloudconvert - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Cloudconvert authorization flow - Return to the terminal and start using Cloudconvert through Claude Code Once authenticated, you can ask Claude Code to perform Cloudconvert operations in natural language. For example: - "Convert a PDF to Word document format" - "Export a converted file directly to S3" - "List all supported video conversion formats" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["cloudconvert"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http cloudconvert-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; 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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['cloudconvert'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http cloudconvert-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Cloudconvert with Claude Code using Composio's MCP server. Now you can interact with Cloudconvert directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Cloudconvert operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Cloudconvert operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## 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 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) - [Vercel AI SDK](https://composio.dev/toolkits/cloudconvert/framework/ai-sdk) - [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 Claude Code? Yes, you can. Claude Code 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)