Dify MCP Server

Dify MCP Server. This is a tool server for Dify Workflow.

Local serverstdio

What is the Dify MCP server?

Dify mcp server connects Dify to AI assistants that speak the Model Context Protocol. Dify MCP Server. This is a tool server for Dify Workflow.

What Dify does

A tool server for easy integration with Dify Workflow using the Model Context Protocol (MCP).

Key capabilities

  • MCP protocol implementation enabling bidirectional communication with Claude
  • Utilizes Dify Workflow as a tool
  • Dynamically retrieves and displays Dify Workflow parameters
  • Simple configuration using environment variables
  • NEW — Support for multiple Dify API keys

Tools it exposes

Once connected, the assistant can call this tool directly:

  • Windows — The Windows tool exposed by this server

Installing the dify 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 3 environment variables: DIFY_BASE_URL, DIFY_API_KEY, DIFY_API_KEYS. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • Node.js 16 or higher - npm 7 or higher - Access rights to Dify Workflow (API Key)

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. Dify sits in that group, and the shape of its toolset — Windows — 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.
  • Maintained by TomokiIshimine.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the dify 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
WindowsThe Windows tool exposed by this server.

How to install the Dify MCP server

{
  "mcpServers": {
    "dify-workflow": {
      "command": "npx",
      "args": ["@tonlab/dify-mcp-server"],
      "env": {
        "DIFY_BASE_URL": "https://your-dify-endpoint",
        "DIFY_API_KEY": "your-api-key-here"
      }
    }
  }
}

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

Configuration

  • Node.js 16 or higher - npm 7 or higher - Access rights to Dify Workflow (API Key)
VariableDescriptionRequired
DIFY_BASE_URLEndpoint or connection string the server talks to.Yes
DIFY_API_KEYCredential the server authenticates with.Yes
DIFY_API_KEYSCredential the server authenticates with.Yes

Example prompts to try

  • Use Dify to Windows.

Frequently asked questions

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