Fire in da houseTop Tip:Paying $100+ per month for Perplexity, MidJourney, Runway, ChatGPT is crazy - get all your AI tools in one site starting at $15 per month with Galaxy AIFire in da houseCheck it out free

mcp-difyworkflow-server

MCP.Pizza Chef: gotoolkits

mcp-difyworkflow-server is an MCP server application designed to integrate with the Dify platform, allowing seamless query and invocation of multiple custom Dify workflows on demand. It supports configuration of multiple workflows and API keys, enabling flexible and scalable automation of complex workflow operations. This server acts as a bridge between MCP clients and the Dify workflow API, facilitating real-time interaction with workflow processes through a standardized MCP interface. It is built in Go and can be easily installed and configured to connect with the Dify platform's API endpoint.

Use This MCP server To

Invoke custom Dify workflows on demand Query status and results of Dify workflows Automate multi-step workflow operations Integrate Dify workflows into AI-enhanced applications Manage multiple Dify workflows with API keys Bridge MCP clients with Dify workflow APIs

README

mcp-difyworkflow-server

mcp-difyworkflow-server is an mcp server Tools application that implements the query and invocation of Dify workflows, supporting the on-demand operation of multiple custom Dify workflows.

INSTALL

git clone https://github.com/gotoolkis/mcp-difyworkflow-server.git

# build by go
cd mcp-difyworkflow-server
go build .

## or use make build
make build

Configuration

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

    The base URL of the Dify platform api server url.

  • "command":"mcp-difyworkflow-server"

    You can specify the absolute path for the compiled binary, or create a symbolic link with:
    "sudo ln -s <gitWorkPath>/mcp-difyworkflow-server /usr/local/bin/mcp-difyworkflow-server"

  • DIFY_WORKFLOW_NAME、DIFY_API_KEYS

    Need to correspond one by one in order.
    Workflow name can be self-defined by the user in the Prompt, and the Workflow API Key needs to be generated for the corresponding workflow created on the Dify platform (refer to the relevant Dify documentation for how to generate the API KEY).

Usage

  • list_workflows
    List authorized workflows
  • execute_workflow
    Execute a specified workflow,args: workflow_name, input Note: The input variable name of the dify workflow should be defined by default as: "message"

Samples

prompt: 查看 mcp-difyworkflow-server 可使用的工具列表
prompt: 给我执行 dify 名为 workflow-translator 的工作流,输入的消息为“这是一条测试消息”

prompt: View the list of tools available for mcp-difyworkflow-server.
prompt: Execute the workflow named 'workflow-translator' for me, the input message is "This is a test message".

mcp-difyworkflow-server FAQ

How do I configure mcp-difyworkflow-server to connect to my Dify platform?
You configure the server by specifying the base URL of your Dify platform API and setting environment variables for workflow names and API keys in the server's configuration JSON.
Can mcp-difyworkflow-server handle multiple workflows simultaneously?
Yes, it supports multiple custom Dify workflows by specifying them in the DIFY_WORKFLOW_NAME environment variable, separated by commas.
What programming language is mcp-difyworkflow-server built with?
It is built using Go, ensuring efficient performance and easy deployment.
How do I install and build mcp-difyworkflow-server?
Clone the GitHub repository, then build the binary using 'go build' or 'make build' commands as described in the README.
Is it possible to secure API keys when using mcp-difyworkflow-server?
Yes, API keys are passed as environment variables (DIFY_API_KEYS), allowing secure management outside of code.
Does mcp-difyworkflow-server support real-time interaction with workflows?
Yes, it enables real-time querying and invocation of workflows through the MCP protocol.
Can mcp-difyworkflow-server be integrated with multiple MCP clients?
Yes, it acts as a server exposing Dify workflows to any MCP client that supports the protocol.
What happens if a workflow invocation fails?
The server returns error information from the Dify API, allowing clients to handle failures appropriately.