Dify Workflows MCP exposes configured Dify applications as assistant tools through a local TypeScript server.
Dify Workflows MCP exposes configured Dify applications as assistant tools through a local TypeScript server.
This integration lets an assistant call Dify applications through MCP instead of recreating their workflow logic. Configuration specifies the Dify base URL and a list of application keys. The exposed operations depend on those applications, so the server’s usefulness follows the workflow definitions and permissions behind them.
The project documents cloning the repository, installing dependencies, building the server and starting the compiled entry point. A CONFIG_PATH variable points to the YAML file when it is stored outside the default location. Keep that file private because it contains application credentials.
The README says the current workflow call uses blocking response mode. It also identifies code and checkResult as expected output fields. If your workflow returns different keys, adapt the integration’s result mapping before relying on the assistant’s answer. Workflow streaming is described as pending rather than an implemented feature.
Use a small Dify application with a known output. Call it with the same input through the application API and the MCP client, then compare the returned fields. Check timeout and error behaviour for a failed workflow. This is a community TypeScript project with ISC licensing, and its installed tools are separate from any official Dify-hosted MCP offering.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| dify_base_url | Dify API 的基本 URL |
| dify_app_sks | Dify 应用程序密钥列表 |
{
"mcpServers": {
"dify-workflow-mcp": {
"command": "node",
"args": [
"/ABSOLUTE_PATH/dify-workflow-mcp/build/index.js"
],
"env": {
"CONFIG_PATH": "/ABSOLUTE_PATH/dify-workflow-mcp/config.yaml"
}
}
}
}Replace both absolute paths and configure Dify base URL and app keys in the YAML file.
Node.js 18 or later, npm and access to a Dify API with application keys.
| Variable | Description | Required |
|---|---|---|
| CONFIG_PATH | Path to the private Dify application configuration. | Optional |
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
Enables AI assistants to interact with and manage n8n workflows through natural language.
Integrate Linear project management with Claude for enhanced workflow automation.
Build and run agents and automations across hundreds of apps using natural language.
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs
Control Adobe After Effects through MCP using a bridge panel running inside AE. This project is optimized for practical automation workflows: effects, presets, keyframing, markers, and audio-aware…