Happy slice of mcp pizzaMCP.pizza

dify-mcp-server

MCP.Pizza Chef: YanxingLiu

Dify is a separate product where people assemble automations without writing code. This makes the ones you have already published available to your assistant as actions it can run: you paste in the secret key for each workflow, and it appears as something the assistant can call. It works in any app that supports MCP, installed either through Smithery or a short configuration block. Be aware that the project has had no commits since April 2025.

Unmaintained · no commits since April 2025; no replacement named
Data
Other

Use This MCP server To

Run one of my Dify workflows straight from a chat Start a saved automation without opening Dify Give my team a workflow they can trigger by asking Feed a workflow's result into whatever I am writing Test a workflow I just published without switching apps

README

Model Context Protocol (MCP) Server for dify workflows

A simple implementation of an MCP server for using dify. It achieves the invocation of the Dify workflow by calling the tools of MCP.

📰 News

  • [2025/4/15] zNow supports directly using environment variables to pass base_url and app_sks, making it more convenient to use with cloud-hosted platforms.

🔨Installation

The server can be installed via Smithery or manually.

Step1: prepare config.yaml or enviroments

You can configure the server using either environment variables or a config.yaml file.

Method 1: Using Environment Variables (Recommended for Cloud Platforms)

Set the following environment variables:

export DIFY_BASE_URL="https://cloud.dify.ai/v1"
export DIFY_APP_SKS="app-sk1,app-sk2" # Comma-separated list of your Dify App SKs
  • DIFY_BASE_URL: The base URL for your Dify API.
  • DIFY_APP_SKS: A comma-separated list of your Dify App Secret Keys (SKs). Each SK typically corresponds to a different Dify workflow you want to make available via MCP.
Method 2: Using config.yaml

Create a config.yaml file to store your Dify base URL and App SKs.

Example config.yaml:

dify-mcp-server FAQ

Is this still maintained?
No. There have been no commits since April 2025. It may still work, but it has not kept up with either Dify or the wider standard, and the author has not named a replacement.
Do I need a Dify account?
Yes. This does nothing on its own — it only exposes workflows you have already built and published in Dify, on their cloud or your own installation.
Do I need a key?
You need the secret key for each Dify workflow you want available, which you list in a small settings file or as environment variables.
Can I use this to trigger an automation just by asking?
Yes — every workflow you add becomes an action your assistant can run on request.
How hard is the setup?
Moderate. You install a small Python runner, list your workflow keys, and paste a block into your assistant's settings. There is also a Smithery listing for a faster install.
Which apps does it work in?
Any app that supports MCP, using the configuration block from the instructions.
Can it build a workflow for me?
No. Building happens inside Dify itself. This only runs what already exists.