Dify MCP Server

Example Use Cases

• 1

  Call and orchestrate multiple Dify applications from a single MCP client interface.

• 2

  Dynamically generated tool interfaces based on remote application parameter specifications.

• 3

  Streaming or blocking responses with built-in retry and large-number (BigInt) handling when interacting with Dify APIs.

Description

This server implements the Model Context Protocol to bridge MCP clients and Dify applications by dynamically fetching application metadata and exposing each app as a tool. It generates tool interfaces from Dify application specifications, supports various input types, and offers both blocking and streaming response modes with retry and BigInt handling. Configuration is done via environment variables (API keys, base URL, timeout), making it easy to integrate with IDEs such as Windsurf.