gotoolkits/DifyWorkflow

Overview

An MCP server written in Go that enables querying and invoking Dify workflows over the Model Context Protocol. It supports on-demand operation of multiple custom Dify workflows, allowing external tools to trigger and retrieve results from Dify-based pipelines.

Best for

Best for
Developers who need to connect Dify workflows to MCP-compatible clients such as AI assistants or automation tools

Use cases

• Querying available Dify workflows from an MCP client
• Invoking specific Dify workflows programmatically
• Integrating custom Dify workflows into LLM-powered applications via MCP

How to use

Install

cd mcp-difyworkflow-server\ngo build .\n# or\nmake build

Example client config

{\n  "mcpServers": {\n    "mcp-difyworkflow-server": {\n      "command": "mcp-difyworkflow-server",\n      "args": ["-base-url", "http://localhost/v1"],\n      "env": {\n        "DIFY_WORKFLOW_NAME": "workflow-translator“,workflow-genImag",\n        "DIFY_API_KEYS": "appkey-xxxxxxxxxxxa,appkey-xxxxxxxxxxxb"\n      }\n    }\n  }\n}

Notes

An MCP server written in Go that enables querying and invoking Dify workflows over the Model Context Protocol. It supports on-demand operation of multiple custom Dify workflows, allowing external tools to trigger and retrieve results from Dify-based pipelines.

58 stars on GitHub. Last updated 2024-12-26. Licensed Apache-2.0.

Use cases

• Querying available Dify workflows from an MCP client
• Invoking specific Dify workflows programmatically
• Integrating custom Dify workflows into LLM-powered applications via MCP

Pros

• Standard MCP interface simplifies integration with AI tools
• Lightweight Go server easy to deploy and run
• Supports multiple Dify workflows without per-workflow configuration

Cons

• Limited community and documentation due to low star count
• Requires an existing Dify platform installation
• Only supports query and invoke, not workflow creation or modification

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.