Dify Workflow MCP server

The Dify Workflows MCP Server offers a TypeScript implementation of Model Context Protocol that exposes Dify workflows as tools. It allows you to transform Dify applications into MCP tools with configuration through YAML files.

Prerequisites

• Node.js 18 or higher
• npm 8 or higher
• Access to Dify API and application keys

Installation

1. Clone the repository:

   git clone https://github.com/localSummer/dify-workflow-mcp
   cd dify-workflow-mcp
   

2. Install dependencies:

   npm install
   

3. Create a configuration file:

   # config.yaml
   dify_base_url: 'https://api.dify.ai/v1'
   dify_app_sks:
     - 'your-dify-app-sk-1' # Replace with your actual Dify application key
     - 'your-dify-app-sk-2' # Replace with your actual Dify application key
   

Usage

1. Build the project:

   npm run build
   

2. Start the server:

   npm start
   

For development environment:

npm run dev

Configuration Options

The server can be configured using a YAML file. By default, it looks for config.yaml in the project root directory. You can specify a different path using the CONFIG_PATH environment variable.

Available Settings

• dify_base_url: Base URL for the Dify API
• dify_app_sks: List of Dify application keys

Client/Roo Integration

To configure the MCP server with a client like Cline or Roo:

"dify-workflow-mcp": {
   "command": "node",
   "args": [
      "path/dify-workflow-mcp/build/index.js"
   ],
   "env": {
      "CONFIG_PATH": "path/dify-workflow-mcp/config.yaml"
   },
   "disabled": false,
   "alwaysAllow": [],
   "timeout": 300
}

Important Notes

• The current workflow implementation uses response mode: 'blocking', which waits for the workflow to complete before outputting final results
• The current workflow output fields are code and checkResult. If your output fields differ, you'll need to adjust the following code:

  const { code, checkResult } = responseData.data.outputs;
  

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.