MCP Server

What is MCP Server?

A Dify endpoint plugin that converts a Dify app into a Model Context Protocol (MCP) server, allowing MCP clients to interact with Dify workflows. It is intended for use within private networks to maintain data security.

How to use MCP Server?

Create a simple workflow app in Dify, add an endpoint and select that app, and ensure the input schema defines parameters (including a query field for chat apps). Then copy the endpoint URL to an MCP client such as Cherry Studio.

Key features of MCP Server?

• Converts a Dify app into an MCP server.
• Simple endpoint-based setup process.
• Supports custom input schema definitions.
• Designed for private network use only.
• Works with standard MCP clients like Cherry Studio.

Use cases of MCP Server?

• Expose Dify workflows as tools for MCP clients.
• Integrate Dify AI capabilities into MCP-compatible applications.
• Create custom internal tools secured within a private network.
• Reuse existing Dify apps as MCP endpoints without additional coding.

FAQ from MCP Servers

What is MCP Server?

MCP Server is a Dify plugin that turns a Dify app into an MCP server, enabling MCP clients to invoke Dify workflows as tools.

How do I configure the input schema for a chat app?

For a chat app, you must include a query field in the input schema, formatted as a JSON object with required properties and a description.

Can I use MCP Server over the public internet?

No. The README explicitly states to use this plugin exclusively within your private network to keep data secure.

Which MCP clients are supported?

The README mentions Cherry Studio as an example, but any standard MCP client should work by pointing it to the endpoint URL.