X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Dify to Claude

Connect Claude Web, Desktop and Cowork to Dify MCP. Run dify workflow to process ticket, fetch dify workflow run history, and more using natural language, with authentication handled for you.

Create my free accountGet a demo
Dify logoDify
Api Key

Dify is a platform for running and managing published workflow apps via a Service API. Use it to execute workflows and inspect configuration and run history quickly.

4 Tools

Introduction

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 Dify account to Claude via Composio Connect, enabling it to run Dify workflow to process ticket, fetch Dify workflow run history, update Dify workflow configuration and test, 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.

Also integrate Dify with

ChatGPTHermes

Connecting Dify 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.

Claude Desktop connectors screen with Add custom connector selected

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

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Dify account

Back in Claude, ask it to connect to Dify or give it any Dify-related task.

For example, ask Claude to:

  • "Run Dify workflow to process ticket"
  • "Fetch Dify workflow run history"
  • "Update Dify workflow configuration and test"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Dify account is ready to use.

What is the Dify Claude Connector, and what's possible with it?

The Dify MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dify account. It provides structured and secure access so your agent can perform Dify operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Dify?

The connector can show as connected, but Claude must use it in each Dify conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Dify again.

2. Why does Claude show an MCP server error before Dify connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Dify.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Dify.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Dify authorization link not work?

The Composio connector is one server. Your Dify account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Dify connection.
  • Composio creates a fresh Dify authorization link.
  • Open that link in your browser and finish the Dify sign-in.

4. Why do Dify actions fail after they worked before?

The Dify connection can expire or lose permission.

  • Ask Claude to inspect the Dify connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Dify account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Dify.
  • If the action still fails with a permission error, check that the connected account has that permission in Dify itself.

5. How do I switch to a different Dify account?

Claude can manage the Dify connection for you.

  • Ask Claude to disconnect or delete the current Dify account.
  • Ask Claude to connect Dify again.
  • Open the new Composio authorization link for Dify.
  • Sign in with the other Dify account in the browser.
  • After the account connects, ask Claude to retry the Dify task.

6. Why is my Dify connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Dify connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Dify tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Dify.
TOOLS

Supported Tools

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

Get Workflow App Configuration

Return the connected Workflow app's identity, declared input form and upload limits, tool icons, and hosted-site settings.

Get Workflow Run

Return one workflow run's status, inputs, arbitrary outputs, error, and execution metrics by run ID.

List Workflow Runs

Return one page of run summaries for the connected Workflow app, with filters and a continuation cursor for older or additional runs.

Run Workflow

Run the connected app's latest published workflow in blocking mode and return its app-defined outputs.

FRAMEWORKS

How to build Dify MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Dify MCP with ChatGPT

Hermes logo

Hermes

Use Dify MCP with Hermes

FAQ

Frequently asked questions

With a standalone Dify MCP server, the agents and LLMs can only access a fixed set of Dify tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dify and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork 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 Dify tools.

Yes, absolutely. You can configure which Dify 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 Dify data and credentials are handled as safely as possible.

Start with Dify.It takes 30 seconds.

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

Start building