Dify Tools MCP Converter

v1.0.0Developer Toolsstable

Converts Dify tools' API to MCP (Model Control Protocol) compatible API, allowing tools created in Dify to be accessed from MCP clients like Cherry Studio.

difydify-pluginsmcpmcp-server
Share:
24
Stars
0
Downloads
0
Weekly
0/5

What is Dify Tools MCP Converter?

Dify Tools MCP Converter is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to converts dify tools' api to mcp (model control protocol) compatible api, allowing tools created in dify to be accessed from mcp clients like cherry studio.

Converts Dify tools' API to MCP (Model Control Protocol) compatible API, allowing tools created in Dify to be accessed from MCP clients like Cherry Studio.

This server falls under the Developer Tools and APIs categories on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • Converts Dify tools' API to MCP (Model Control Protocol) com

Use Cases

Convert custom Dify tools to MCP-compatible APIs for use in Cherry Studio and other MCP clients.
Extend Dify plugins to work with external AI agent platforms.
junjiem

Maintainer

LicenseMIT
Languagepython
Versionv1.0.0
UpdatedMar 29, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx dify-tools-mcp-converter

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use Dify Tools MCP Converter

The Dify Tools MCP Converter is a Dify 1.0 plugin that converts your custom Dify tools' API endpoints into MCP-compatible APIs, enabling them to be accessed from any MCP client such as Cherry Studio, Claude, or Cursor. It supports both Streamable HTTP (recommended) and HTTP with SSE transports, and requires Dify version 1.2.0 or higher. Once installed, you configure endpoints in the Dify platform UI and simply copy the generated MCP URL into your MCP client.

Prerequisites

  • Dify platform version 1.2.0 or higher (self-hosted or cloud)
  • Existing Dify tools configured in your Dify workspace
  • An MCP client such as Cherry Studio, Claude Desktop, or Cursor
  • Access to the Dify plugin management page
1

Install the plugin via GitHub

In the Dify platform, navigate to the plugin management page. Choose to install via GitHub, enter the repository address, and select the version and package file.

# GitHub repository URL for installation:
https://github.com/junjiem/dify-plugin-mcp_compat_dify_tools
2

Handle plugin signature verification (if needed)

If you see 'plugin verification has been enabled, and the plugin you want to install has a bad signature', add the following line to your Dify .env file to allow unsigned plugins.

FORCE_VERIFYING_SIGNATURE=false
3

Add an endpoint and configure the tool list

After installation, open the plugin in Dify and add an API endpoint. Then add the Dify tools you want to expose via MCP to the tool list for that endpoint. Save the endpoint configuration.

4

Copy the MCP endpoint URL

After saving, Dify generates two MCP URLs: one for Streamable HTTP (recommended) and one for legacy HTTP with SSE. Copy the URL for your preferred transport.

5

Configure your MCP client with the endpoint URL

Paste the copied URL into your MCP client configuration. For Cherry Studio, add it in the MCP server settings. For other clients, add it as a remote MCP server URL.

6

Update tool list changes

If you modify the tool list for an existing endpoint, you must disable and then re-enable the endpoint in Dify for the changes to take effect.

Dify Tools MCP Converter Examples

Client configuration

Example MCP client config using the Streamable HTTP transport URL generated by the Dify plugin. Replace the URL with your actual Dify endpoint URL.

{
  "mcpServers": {
    "dify-tools": {
      "command": "npx",
      "args": ["dify-tools-mcp-converter"],
      "env": {
        "DIFY_ENDPOINT_URL": "https://your-dify-instance/mcp/your-endpoint-id"
      }
    }
  }
}

Prompts to try

Once Dify tools are exposed as MCP tools, MCP clients can discover and invoke them naturally.

- "List the available tools from my Dify workspace."
- "Use the Dify weather tool to get the current weather in Tokyo."
- "Run the document summarization tool from Dify on this text: ..."
- "Call the Dify search tool to find information about AI model context protocol."
- "Use my Dify data analysis tool to process this CSV data."

Troubleshooting Dify Tools MCP Converter

Plugin installation fails with 'bad signature' error

Add FORCE_VERIFYING_SIGNATURE=false to the end of your Dify .env configuration file. This allows installing plugins not listed in the Dify Marketplace. Restart Dify after making this change.

Tool list changes are not reflected in the MCP client

Modifications to the tool list for an existing endpoint only take effect after disabling and re-enabling the endpoint in the Dify plugin UI. After toggling, reconnect your MCP client to refresh the tool list.

MCP client cannot connect to the Dify endpoint URL

Ensure your Dify instance is accessible from the MCP client's network. For self-hosted Dify, check firewall rules and that the plugin's HTTP service is running. Use the Streamable HTTP transport URL rather than the SSE URL for better compatibility with modern MCP clients.

Frequently Asked Questions about Dify Tools MCP Converter

What is Dify Tools MCP Converter?

Dify Tools MCP Converter is a Model Context Protocol (MCP) server that converts dify tools' api to mcp (model control protocol) compatible api, allowing tools created in dify to be accessed from mcp clients like cherry studio. It connects AI assistants to external tools and data sources through a standardized interface.

How do I install Dify Tools MCP Converter?

Follow the installation instructions on the Dify Tools MCP Converter GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with Dify Tools MCP Converter?

Dify Tools MCP Converter works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is Dify Tools MCP Converter free to use?

Yes, Dify Tools MCP Converter is open source and available under the MIT license. You can use it freely in both personal and commercial projects.

Browse More Developer Tools MCP Servers

Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "dify-tools-mcp-converter": { "command": "npx", "args": ["-y", "dify-tools-mcp-converter"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use Dify Tools MCP Converter?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides