Dify Workflow

Queries and invokes on-demand Dify workflows via MCP using per-workflow API keys.

go

59

GitHub Stars

go

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "gotoolkits-mcp-difyworkflow-server": {
      "command": "mcp-difyworkflow-server",
      "args": [
        "-base-url",
        "http://localhost/v1"
      ],
      "env": {
        "DIFY_API_KEYS": "appkey-xxxxxxxxxxxa,appkey-xxxxxxxxxxxb",
        "DIFY_WORKFLOW_NAME": "workflow-translator,workflow-genImag"
      }
    }
  }
}

You can query and invoke multiple on-demand Dify workflows through this MCP server tool. It translates your prompts into workflow calls and returns the results, letting you orchestrate custom Dify workflows from your MCP client.

How to use

You will interact with this server through an MCP client by listing available workflows and executing a chosen workflow with input. Use the available tools to see which workflows you can call, then run the one that matches your task. The input expected by a Dify workflow is typically mapped to a field named message in the workflow payload.

How to install

Prerequisites you need before installing this server:

# Install Go and Git if you don’t have them
# On macOS with Homebrew
brew install go git

# On Debian/Ubuntu
sudo apt-get update
sudo apt-get install -y golang-go git

Clone the project, build the binary, and optionally use a provided build target.

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

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

## or use make build
make build

Configuration

Configure the MCP server to run the Dify workflow connector and connect it to your Dify platform. The base URL for the Dify platform API is provided in the startup arguments, and you supply the workflow names and API keys so the server can call the correct workflows.

{
  "mcpServers": {
    "difyworkflow": {
      "command": "mcp-difyworkflow-server",
      "args": ["-base-url", "http://localhost/v1"],
      "env": {
        "DIFY_WORKFLOW_NAME": "workflow-translator,workflow-genImag",
        "DIFY_API_KEYS": "appkey-xxxxxxxxxxxa,appkey-xxxxxxxxxxxb"
      }
    }
  }
}

Notes on configuration details

The base URL field sets the Dify platform API endpoint. Use the exact URL provided when you deploy your Dify workflows.
The command field must point to the compiled binary for the MCP server, or you can create a symbolic link to a system path for convenience.
DIFY_WORKFLOW_NAME and DIFY_API_KEYS must correspond by position. Each workflow you intend to call should have a matching API key generated in the Dify platform.

Examples

Use the following prompts to interact with the server from your MCP client:

List available workflows to confirm what you can call.
Execute the workflow named workflow-translator with an input message like: This is a test message.

Available tools

list_workflows

Retrieves the authorized workflows that can be invoked through the MCP server.

execute_workflow

Runs a specified Dify workflow using the provided input, with the default input variable named message.