📌Overview

Purpose: The MCP Server plugin transforms a Dify app into a multi-channel processing (MCP) server, facilitating seamless data handling within private networks.

Overview: This Dify endpoint plugin enhances the functionality of Dify applications by enabling them to operate as MCP servers, thus providing a robust solution for managing data securely within private settings.

Key Features:

Data Transformation: Converts a Dify app into an MCP server, allowing for multi-channel data processing while maintaining data security.
Input Schema Definition: Requires a structured input schema, ensuring compatibility and smooth integration with various data types and operations within the application.

MCP Server

Author: hjlarry
Version: 0.0.2
Type: extension
Repo: https://github.com/hjlarry/dify-plugin-mcp_server
Feature Request: https://github.com/hjlarry/dify-plugin-mcp_server/issues

A Dify endpoint plugin that changes a Dify app to an MCP server.

To keep your data secure, use this plugin exclusively within your private network.

Get Started

1. Create a simple workflow app in Dify.

2. Add an endpoint and select this app.

The app's input schema must define its input parameters. For a chat Dify app, ensure to include a query field in the input schema, formatted as follows:

{
    "name": "get_weather",
    "description": "Get weather status for a place.",
    "inputSchema": {
        "properties": {
            "place": {"title": "Place", "type": "string"}
        },
        "required": ["place"],
        "title": "get_weatherArguments",
        "type": "object"
    }
}

dify-plugin-mcp_server

📌Overview

MCP Server

Get Started

1. Create a simple workflow app in Dify.

2. Add an endpoint and select this app.

3. Copy the endpoint URL to your MCP client, like Cherry Studio.

Option 1: Use the newest Streamable HTTP protocol (Recommended)

Option 2: Use the legacy SSE protocol

4. Enjoy it!

Changelog

0.0.2