Transforms a Dify application into a Message Communication Protocol (MCP) server endpoint.
Sponsored
This Dify endpoint plugin allows users to convert any Dify workflow application into a functional MCP server. It facilitates seamless integration with MCP clients like Cherry Studio by exposing Dify app functionalities as a server endpoint. Users can define input schemas for their Dify apps and connect via either the modern Streamable HTTP protocol or the legacy SSE protocol. Emphasizing data security, the plugin recommends usage within private networks and supports Auth Bearer Token validation for secure client-server communication. It also includes health check responses and enhanced logging for debugging.
Key Features
010 GitHub stars
02Supports both Streamable HTTP and legacy SSE protocols for client communication
03Converts Dify applications into MCP server endpoints
04Provides `ping` method response for server health checks
05Enables definition of input schemas for Dify chat applications (e.g., query field)
06Implements Auth Bearer Token validation for secure access
Use Cases
01Integrating Dify-powered AI assistants or tools with MCP-compatible frontends
02Securing Dify application endpoints with bearer tokens for controlled access
03Exposing Dify workflow applications to MCP clients for integration
