MCP Server

What is MCP Server?

A Dify endpoint plugin that turns a Dify app into an MCP server, allowing it to be used with MCP clients like Cherry Studio. Designed for private network use.

How to use MCP Server?

Create a simple workflow app in Dify, add an endpoint selecting this app, define the input schema (include a query field for chat apps), then copy the endpoint URL to an MCP client. Optionally set an Auth Bearer Token for security.

Key features of MCP Server

• Converts a Dify app into an MCP server.
• Supports Streamable HTTP and legacy SSE protocols.
• Customizable input schema via JSON endpoint settings.
• Optional Bearer token authentication.
• Responds to MCP ping method for health checks.

Use cases of MCP Server

• Exposing a Dify weather app as an MCP tool.
• Integrating Dify workflow apps into MCP‑compatible assistants.
• Hosting a private MCP server securely within a network.

FAQ from MCP Server

What protocols does MCP Server support?

Streamable HTTP (recommended) and legacy SSE.

How do I add authentication?

Set an Auth Bearer Token in the endpoint settings. The MCP client must include Authorization: Bearer <token> in its request header.

Can I use this plugin outside my private network?

No, the README advises using it exclusively within your private network for data security.

What is the required input schema format?

A JSON object with name, description, and inputSchema containing properties and required. For chat apps, include a query field.

How does the plugin handle the ping method?

Starting from version 0.0.4, it responds to the MCP ping method, which some clients use to check server health.