alexjiaguo

Dify MCP — Testing skill for Claude Code

Testing community

The most complete Dify MCP server + CLI - 138 tools that let any AI agent build, test & ship Dify workflows autonomously.

How to install Dify MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open alexjiaguo/dify-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Dify MCP does

The most complete Dify MCP server + CLI - 138 tools that let any AI agent build, test & ship Dify workflows autonomously. Works with Claude Code, Codex, Gemini, Cursor.

Alternatives in Testing

  • Spec Kitty — Spec-Driven Development for serious software developers 1.6k ★
  • Spectra App — Spec-driven development for coding agents — a desktop app, a CLI, and skills for Codex, Claude Code, Cursor, C 735 ★
  • Mda — MDA Open Spec — a Markdown superset for agent-facing documents 615 ★

README

dify-mcp

The most complete MCP server + CLI for [Dify](https://github.com/langgenius/dify)

**143 tools. 16 namespaces. One registry.** Let any AI agent build, test, and ship Dify workflows autonomously — everything a human can do in the UI, now scriptable.

[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE) [![Node >= 23.6](https://img.shields.io/badge/node-%E2%89%A523.6-green.svg)](https://nodejs.org) [![143 Tools](https://img.shields.io/badge/tools-143-purple.svg)](#tools) [![Live Verified](https://img.shields.io/badge/live--verified-cloud.dify.ai-brightgreen.svg)](#live-verified)

Works with **Claude Code** · **Codex** · **Gemini CLI** · **Cursor** · **Cline** · **Windsurf** · **Roo Code** · **Continue** · **Aider** · **Zed** — and any other MCP-compatible or shell-capable agent.


What is this?

Dify is a powerful open-source LLM app platform — but its workflow builder is a **visual drag-and-drop editor**. What if you want an AI agent to *programmatically* create workflows, wire up nodes, test them, iterate, and publish — without a browser?

**dify-mcp** is the bridge. It exposes the **entire Dify console API** as a unified tool registry with **two surfaces**: a CLI any shell-capable agent can drive, and an MCP server (stdio or Streamable HTTP) any MCP-compatible host can attach. Same 143 tools, same JSON contract, same safety guarantees.

┌──────────────────────────────────────────────────────────┐
│                    dify-mcp                              │
│                                                          │
│   ┌──────────┐    ┌────────────────────┐    ┌─────────┐ │
│   │  CLI     │───▶│   143-tool         │───▶│  Dify   │ │
│   │  difywf  │    │   registry         │    │  API    │ │
│   └──────────┘    │                    │    └─────────┘ │
│   ┌──────────┐    │  app · workflow    │         ▲      │
│   │  MCP     │───▶│  provider · rag    │─────────┘      │