LABSCO SUMMARY

Environment variables are enough — no config file needed on a cloud platform.

Being able to pass the base URL and the secret keys directly as environment variables is what makes this deployable somewhere you cannot drop a YAML file. Otherwise the model is simple and holds up: one App Secret Key per workflow, listed in order, and whatever you built in Dify becomes callable from the assistant you already use.

What it is

A bridge that turns Dify workflows into MCP tools. Each Dify App Secret Key you list becomes a workflow the client can invoke.

What you get

Your Dify workflows callable as tools from any MCP-capable client
Several workflows at once — the SK list is comma-separated, and each key typically maps to a different workflow
Two ways to configure: environment variables, or a config.yaml with dify_base_url and dify_app_sks
Cloud-hosted or self-hosted Dify, since the base URL is yours to set

Requirements

uv or uvx. Set DIFY_BASE_URL to your Dify API base — https://cloud.dify.ai/v1 for the hosted service — and DIFY_APP_SKS to a comma-separated list of App Secret Keys. Alternatively write a config.yaml and point CONFIG_PATH at it. Run with uvx --from the repository git URL and dify_mcp_server, or clone and run it with uv.

Setup effort

Add the configuration to your client

See installation options

USE CASES

01

Reusing a workflow outside Dify's own interface

Point the server at its secret key and call it from Claude, Cursor or anything else that speaks MCP.

02

Exposing several workflows to one assistant

List the App Secret Keys comma-separated and each becomes callable.

03

Running against a self-hosted Dify

Set the base URL to your own instance instead of the cloud endpoint.

04

Deploying where you cannot write a config file

Pass the base URL and keys as environment variables instead.

BEFORE YOU INSTALL

What to know first

Requires

DIFY_APP_SKS in your environment

INSTALLATION

Connect your client

This one is configured rather than run — your client needs the configuration block, not a command.

Server setup

JSON

{
  "mcpServers": {
    "dify-mcp-server": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/YanxingLiu/dify-mcp-server",
        "dify_mcp_server"
      ],
      "env": {
        "DIFY_BASE_URL": "https://cloud.dify.ai/v1",
        "DIFY_APP_SKS": "app-sk1,app-sk2"
      }
    }
  }
}

Dify Workflows