Dify Workflow

Dify Workflow

tomokiishimine

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.

Connects Claude with Dify Workflow to expose workflow capabilities as tools, enabling structured automation through dynamic parameter retrieval and multi-workflow support.

81,669 views2Local (stdio)

What it does

  • 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

Best for

Automating business processes through ClaudeIntegrating existing Dify workflows into AI conversationsRunning multi-step workflows without leaving ClaudeTeams using Dify for workflow automation
Multiple API key supportDynamic parameter detectionSimple environment variable setup

About Dify Workflow

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

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.

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

Alternatives

Related Skills

Browse all skills
unity-mcp-orchestrator

Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.

0
crewai-developer

Comprehensive CrewAI framework guide for building collaborative AI agent teams and structured workflows. Use when developing multi-agent systems with CrewAI, creating autonomous AI crews, orchestrating flows, implementing agents with roles and tools, or building production-ready AI automation. Essential for developers building intelligent agent systems, task automation, and complex AI workflows.

0
godot

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

398
ui-ux-expert-skill

Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.

46
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

6
gpt-researcher

GPT Researcher is an autonomous deep research agent that conducts web and local research, producing detailed reports with citations. Use this skill when helping developers understand, extend, debug, or integrate with GPT Researcher - including adding features, understanding the architecture, working with the API, customizing research workflows, adding new retrievers, integrating MCP data sources, or troubleshooting research pipelines.

4