Dify Workflow▌

by tomokiishimine
Streamline tasks with Dify Workflow—powerful workflow automation software for automated approval and advanced workflow a
Connects Claude with Dify Workflow to expose workflow capabilities as tools, enabling structured automation through dynamic parameter retrieval and multi-workflow support.
best for
- / Automating business processes through Claude
- / Integrating existing Dify workflows into AI conversations
- / Running multi-step workflows without leaving Claude
- / Teams using Dify for workflow automation
capabilities
- / Execute Dify workflows from Claude
- / Retrieve workflow parameters dynamically
- / Configure multiple Dify API keys
- / Access different Dify endpoints
- / Run structured automation workflows
- / Pass parameters to workflow executions
what it does
Connects Claude to Dify Workflow APIs, allowing you to execute Dify workflows directly from Claude conversations. Supports multiple API keys for accessing different workflow collections.
about
Dify Workflow is a community-built MCP server published by tomokiishimine that provides AI assistants with tools and capabilities via the Model Context Protocol. Streamline tasks with Dify Workflow—powerful workflow automation software for automated approval and advanced workflow a It is categorized under productivity, developer tools.
how to install
You can install Dify Workflow in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Dify Workflow is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Dify Workflow MCP Tool Server
A tool server for easy integration with Dify Workflow using the Model Context Protocol (MCP).
Features
- MCP protocol implementation enabling bidirectional communication with Claude
- Utilizes Dify Workflow as a tool
- Dynamically retrieves and displays Dify Workflow parameters
- Simple configuration using environment variables
- NEW: Support for multiple Dify API keys
Prerequisites
- Node.js 16 or higher
- npm 7 or higher
- Access rights to Dify Workflow (API Key)
Integration with Claude Desktop App
To use with Claude Desktop App, add the following settings to Claude's configuration file:
Windows
Add to %AppData%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"dify-workflow": {
"command": "npx",
"args": ["@tonlab/dify-mcp-server"],
"env": {
"DIFY_BASE_URL": "https://your-dify-endpoint",
"DIFY_API_KEY": "your-api-key-here"
}
}
}
}
Using Multiple API Keys (NEW)
You can now configure multiple Dify API keys, which will create multiple tools (one per API key):
{
"mcpServers": {
"dify": {
"command": "npx",
"args": ["@tonlab/dify-mcp-server"],
"env": {
"DIFY_BASE_URL": "https://api.dify.ai/v1",
"DIFY_API_KEYS": "app-FirstAPIKeyHere,app-SecondAPIKeyHere,app-ThirdAPIKeyHere"
}
}
}
}
Each API key will be exposed as a separate tool in Claude, with a distinct number appended to the tool name.
macOS/Linux
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"dify-workflow": {
"command": "npx",
"args": ["@tonlab/dify-mcp-server"],
"env": {
"DIFY_BASE_URL": "https://your-dify-endpoint",
"DIFY_API_KEY": "your-api-key-here"
}
}
}
}
Same multiple API key configuration as described above works on macOS/Linux as well.
License
MIT
FAQ
- What is the Dify Workflow MCP server?
- Dify Workflow is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Dify Workflow?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Dify Workflow is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Dify Workflow against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Dify Workflow is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Dify Workflow reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Dify Workflow for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Dify Workflow surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Dify Workflow has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Dify Workflow benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Dify Workflow into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Dify Workflow is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.