DifyWorkflow MCP Server

Tools to the query and execute of Dify workflows

Local serverstdioGo

What is the DifyWorkflow MCP server?

Difyworkflow mcp server lets Claude, Cursor and other MCP clients work with DifyWorkflow directly. Tools to the query and execute of Dify workflows.

What DifyWorkflow does

mcp-difyworkflow-server is an mcp server Tools application that implements the query and invocation of Dify workflows, supporting the on-demand operation of multiple custom Dify workflows.

Tools it exposes

Once connected, the assistant can call this tool directly:

  • Samples — The Samples tool exposed by this server

Installing the difyworkflow mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: DIFY_WORKFLOW_NAME, DIFY_API_KEYS. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. DifyWorkflow sits in that group, and the shape of its toolset — Samples — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Written in Go.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the difyworkflow mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
SamplesThe Samples tool exposed by this server.

How to install the DifyWorkflow MCP server

## Configuration

```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": "appkey-xxxxxxxxxxxa,appkey-xxxxxxxxxxxb"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DIFY_WORKFLOW_NAMEConfiguration value read at startup.Optional
DIFY_API_KEYSCredential the server authenticates with.Yes

Example prompts to try

  • Use DifyWorkflow to Samples.

Frequently asked questions

It connects DifyWorkflow to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Samples) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with DifyWorkflow directly.