MCP.so
登录

Dify as MCP Server

@Yevanchen

基本信息

分类

其他

传输方式

stdio

作者

Yevanchen

关于 Dify as MCP Server

暂无概览

Dify as MCP Server 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

Dify as MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Dify as MCP Server?

Dify as MCP Server is a Dify plugin that exposes Dify workflows as a Model Context Protocol (MCP) server for AI clients like Claude Desktop and Cursor. It allows AI assistants to discover and invoke Dify workflows as tools without modifying the workflows themselves.

How to use Dify as MCP Server?

Install the plugin in Dify, configure the plugin settings by providing the application ID of the workflow to expose. Then in your MCP-compatible client (such as Claude Desktop or Cursor), add a new MCP server with the URL https://<your-dify-instance>/difyapp_as_mcp_server, save, and enable the server.

Key features of Dify as MCP Server

  • Exposes Dify workflows as MCP tools to AI clients
  • Supports JSON-RPC over SSE and Streamable HTTP
  • Automatic tool discovery and registration from workflows
  • Compatible with Claude Desktop, Cursor, and other MCP clients
  • Server-side session management with heartbeat (≈5 minutes)
  • Implements the latest MCP Streamable HTTP specification

Use cases of Dify as MCP Server

  • Enable Claude to call Dify workflows as built-in tools
  • Integrate custom AI assistants with any Dify automation pipeline
  • Provide tool access to Cursor agents during development
  • Deploy a stateless MCP server in a Dify plugin environment

常见问题

1

What AI clients are supported?

Claude Desktop, Cursor, and any MCP-compatible client that supports SSE or Streamable HTTP.

2

How do I configure the plugin?

Set the application ID of the Dify workflow you want to expose. Ensure the workflow is published and the Dify API key has sufficient permissions.

3

Does it require a persistent connection?

No. The plugin supports a stateless server mode where each request is independent and associated via session ID, suitable for Dify’s stateless API environment.

4

How do I troubleshoot tool visibility?

Verify the server URL is correct and accessible, the app ID is configured correctly, the workflow is published, and the Dify API key has appropriate permissions.

5

What transport does the server use?

It uses a GET endpoint for SSE connections and HTML pages, and a POST endpoint for JSON-RPC requests, following the MCP Streamable HTTP spec.

评论

其他 分类下的更多 MCP 服务器