Dify Tools MCP Converter
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.
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
Maintainer
Works with
Installation
Manual Installation
npx dify-tools-mcp-converterConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
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
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_toolsHandle 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=falseAdd 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.
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.
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.
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.
Dify Tools MCP Converter Alternatives — Similar Developer Tools Servers
Looking for alternatives to Dify Tools MCP Converter? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.
Ecc
★ 188.2kThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Javaguide
★ 155.8kJava 面试 & 后端通用面试指南,覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Gemini CLI
★ 104.5kA secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in
Awesome MCP Servers
★ 87.3k⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.
MCP Servers
★ 86.0kModel Context Protocol Servers
CC Switch
★ 77.5kA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
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.
Set Up Dify Tools MCP Converter in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
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.