Name: DifyWorkflow
Author: gotoolkits

LABSCO SUMMARY

Workflows you already built, reachable from the assistant you already use.

The design is deliberately narrow: the allowed workflows and their keys are fixed when the server starts, so a model can only call what you listed. Two details decide whether it works first time - the name and key lists must be in the same order, and the workflow's input variable has to be called message.

What it is

A small Go server that fronts Dify workflows. You list which workflows it may reach and their API keys at launch; the client can then see them and run one by name with an input message.

What you get

List the workflows this server has been authorised to call
Execute one by name with an input, and get the workflow's result back
Several custom workflows behind one server, selected per call rather than per deployment

Requirements

Go to build, then either put the binary on your PATH or reference it by absolute path in the client config. Point it at your Dify API base URL with the base-url argument. Two environment variables carry the mapping: DIFY_WORKFLOW_NAME with the workflow names you choose, and DIFY_API_KEYS with the matching keys generated in Dify - the two lists must line up in order. On the Dify side, the workflow's input variable should be named message.

Setup effort

Build from source — git clone https://github.com/gotoolkits/mcp-difyworkflow-server.git

See installation options

USE CASES

01

Reusing a Dify workflow inside a coding assistant

Register the workflow and its key, then call it by name from the client instead of switching to the Dify UI.

list_workflowsexecute_workflow

02

Offering several workflows without several servers

List each name against its key and let the model pick per call.

list_workflows

03

Keeping workflow keys out of the client

Keys live in the server's environment, so the MCP client only ever sees workflow names.

execute_workflow

2 tools

Listed in project docs. Your client may show a different list.

list_workflows

execute_workflow

BEFORE YOU INSTALL

What to know first

Tools you get

2 tools named in the project's documentation.

Requires

DIFY_API_KEYS in your environment

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

This one is built from source rather than installed with a single command.

Server setup

TERMINAL

git clone https://github.com/gotoolkits/mcp-difyworkflow-server.git

# build by go
cd mcp-difyworkflow-server
go build .

## or use make build
make build

MCP Clients

Any MCP client

ANY MCP CLIENT · JSON

{
  "mcpServers": {
    "mcp-difyworkflow-server": {
      "command": "mcp-difyworkflow-server",
      "args": [
        "-base-url",
        "http://localhost/v1"
      ],
      "env": {
        "DIFY_WORKFLOW_NAME": "workflow-translator,workflow-genImag",
        "DIFY_API_KEYS": "<YOUR_DIFY_API_KEYS>,<YOUR_APPKEY_XXXXXXXXXXXB>"
      }
    }
  }
}

DifyWorkflow