Advertise
MCP.so
Sign In

Dify as MCP Server

@Yevanchen

Repository

Basic information

Category

Other

Transports

stdio

Author

Yevanchen

About Dify as MCP Server

No overview available yet

Dify as MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Dify as MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

Frequently asked questions

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.

Comments

More Other MCP servers

Volley.sh

Volley

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi

Senso MCP for Joomla

sensomedia

Senso MCP turns a Joomla 5 or 6 site into a remote MCP server. It runs inside Joomla itself (no extra server, no Node.js bridge) and is secured with OAuth 2.1 and Joomla's own ACL. The free pack lets an AI assistant crea

MCP Toolbox for Databases

googleapis

MCP Toolbox for Databases is an open source MCP server for databases.

15.9K

LoadOptimizer

LoadOptimizer plans truck, container and pallet loads with a real optimization engine, straight from your AI assistant. Describe the order in plain language, for example "plan 36 Euro pallets on a standard 13.6 m trailer

EverArt

modelcontextprotocol

Model Context Protocol Servers

88.1K
Advertise