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. This is a tool server for Dify Workflow. That is what the dify mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

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

  • 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

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Windows — The Windows tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: DIFY_BASE_URL, DIFY_API_KEY, DIFY_API_KEYS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

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

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dify's toolset — Windows — is a fair guide to whether it matches your workflow. It is maintained by sultanlive; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

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.