What dependencies or runtime are required?
The server is a compiled Go binary. You only need the binary and a Dify platform with an accessible API endpoint.
Gotoolkits_mcp Difyworkflow Server MCP Server
@MCP-Mirror
Basic information
About Gotoolkits_mcp Difyworkflow Server MCP Server
Mirror of
Gotoolkits_mcp Difyworkflow Server MCP Server config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryGotoolkits_mcp Difyworkflow Server MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Gotoolkits_mcp Difyworkflow Server?
Gotoolkits_mcp Difyworkflow Server is an MCP server Tools application that lets you query and invoke Dify workflows on demand, supporting multiple custom workflows simultaneously. It is built for developers using the Dify platform who want to trigger workflows via an MCP client.
How to use Gotoolkits_mcp Difyworkflow Server?
Clone the repository, build the binary with Go or make, then configure the server in your MCP client’s settings JSON. Set the Dify API base URL via -base-url, and provide comma-separated workflow names and API keys via the environment variables DIFY_WORKFLOW_NAME and DIFY_API_KEYS. Use the tools list_workflows to list authorized workflows and execute_workflow to run one by name, passing the input as message.
Key features of Gotoolkits_mcp Difyworkflow Server
- Lists all authorized Dify workflows.
- Executes any named workflow with custom input.
- Supports multiple workflows with one-to-one name/key mapping.
- Uses the Dify platform API for all operations.
- Works with any MCP‑compatible client.
Use cases of Gotoolkits_mcp Difyworkflow Server
- Trigger a translation workflow from an AI assistant.
- Run a content generation workflow by name.
- Automate multi‑step Dify pipelines via MCP tools.
- Integrate Dify workflows into larger MCP‑based toolchains.
Frequently asked questions
How are workflow names and API keys configured?
Set `DIFY_WORKFLOW_NAME` and `DIFY_API_KEYS` as comma‑separated lists. The order must correspond one‑to‑one – the first name maps to the first key, and so on.
What transport or authentication does the server use?
It communicates with the Dify API via the base URL you provide (e.g., `http://localhost/v1`). Authentication is handled by the API keys supplied in the environment.
What is the expected input variable name for a Dify workflow?
The Dify workflow’s input variable should be defined as "message". The `execute_workflow` tool passes the user’s input under that key.
Are there any limitations on workflow names or keys?
No limits are stated beyond the requirement that names and keys be provided in matching order. The server supports multiple workflows but the exact maximum is not specified.
More Other MCP servers
Handl
Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
Blender
ahujasidOpen-source MCP to use Blender with any LLM
23.6K
Figs, Relationship Expert
Figs O'Sullivan, LMFTCouples therapist Figs O'Sullivan (LMFT, 17 years, endorsed by Sue Johnson, creator of EFT) inside your AI. Ask relationship questions answered from his clinical writing, name the pattern in a fight, get a three-step rep
Maestro
mobile-dev-incPainless E2E Automation for Mobile and Web
14.8K
N
Next Generation Movers: free moving quotes (remote MCP)
Next Generation MoversFree moving quotes for AI agents from Next Generation Movers, a licensed interstate mover (USDOT 3764697). US long-distance nationwide and local DC/MD/VA. Indicative ballpark price and booking options; optional $0.01 x40
Comments