How to connect Composio to Claude

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Composio account to Claude via Composio Connect, enabling it to generate a step-by-step workflow plan, check active connections for all toolkits, download public S3 file to local path, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Connecting Composio to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Click Add custom connector and paste in the Composio MCP server URL:

The Composio MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Composio account. It provides structured and secure access to your connected tools, so your agent can plan workflows, orchestrate complex actions, manage integrations, and execute cross-tool automations on your behalf.

• Automated workflow planning and execution: The agent can generate and run step-by-step plans for complex, multi-tool use cases—ensuring tasks are completed reliably, even when they span multiple services.
• Connection management and discovery: Effortlessly check the status of multiple toolkit connections, discover what integrations are active, and manage how your agent connects to different services.
• Tool and dependency exploration: Ask your agent to map out tool dependencies, discover related tools, and understand which tools work best together for your workflow.
• Direct code and command execution: Let the agent run code snippets or shell commands in supported environments, tying together automation across your stack.
• Bulk and parallel operations: Use specialized tools for parallel execution or to handle many similar tasks at once—speeding up large automations by making multiple calls in a single workflow.