Dify Plugin MCP Compat Dify Tools

🚀 Dify 1.0 Plugin: Convert Dify Tools' APIs to MCP-Compatible APIs

This plugin converts the APIs of Dify tools into MCP-compatible APIs, enabling seamless integration with MCP clients.

Author: Junjie.M
Type: Extension
GitHub Repository: https://github.com/junjiem/dify-plugin-mcp_compat_dify_tools
GitHub Issues: issues

Reference: https://github.com/hjlarry/dify-plugin-mcp_server

🚀 Quick Start

Prerequisites

⚠️ Important Note

You must use Dify version 1.2.0 or higher.

Steps to Convert APIs

1. Add an Endpoint and Tool List

Step-by-step Instructions:

1. Add a new API endpoint on the Dify platform.
2. Configure the tool list for this endpoint and ensure its accuracy.
3. Save the settings after configuration.

Example Screenshots:

• Add Endpoint:
• Add Tool List:
• Edit Tool:
• Save Endpoint:

⚠️ Important Note

If you modify the tool list of an existing endpoint, you need to disable the endpoint first and then re - enable it for the changes to take effect.

2. Copy the Endpoint URL to Your MCP Client (e.g., Cherry Studio)

Step-by-step Instructions:

1. Find the configured endpoint URL on the Dify platform.
2. Copy and paste this URL into the relevant settings of your MCP client (such as Cherry Studio).

Example Screenshots:

• Example of MCP-supported URLs:

Option 1: Use the Latest Streamable HTTP Transmission Method (Recommended)

1. Select the Streamable HTTP mode when configuring the endpoint.
2. Set the corresponding parameters in Cherry Studio to support this transmission method.

Example Screenshots:

• Example of Streamable HTTP URL in MCP:
• Example of Streamable HTTP Configuration in Cherry Studio:

Done!

Option 2: Use the Traditional HTTP with SSE Transmission Method

1. Select the HTTP with SSE mode when configuring the endpoint.
2. Set the corresponding parameters in Cherry Studio to support this transmission method.

Example Screenshots:

• Example of HTTP with SSE URL in MCP:
• Example of HTTP with SSE Configuration in Cherry Studio:

📚 Documentation

Frequently Asked Questions (FAQ)

1. What should I do if I encounter a signature verification error when installing the plugin?

   • Solution: Modify the environment variables to bypass signature verification. Refer to the documentation or contact technical support for specific operations.

2. How can I install the offline version of the plugin?

   • Answer: A GitHub repository address https://github.com/hjlarry/dify-plugin-mcp_server is provided. You can use a script to download and repackage the offline package.

By following the above steps, you can configure an MCP-compatible API endpoint on the Dify platform and successfully integrate it into clients such as Cherry Studio. If you have other questions, please refer to the relevant documentation or contact technical support.