MCP.so
Sign In

dify-mcp-client

@3dify-project

Repository

About dify-mcp-client

MCP Client as an Agent Strategy Plugin. Support GUI operation via UI-TARS-SDK.

#mcp#dify#dify-plugins#mcp-clients

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "dify-mcp-client": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "dify-mcp-client:latest",
        "."
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is dify-mcp-client?

dify-mcp-client is a Dify plugin that acts as an MCP (Model Context Protocol) Host, connecting MCP servers into Dify workflows as a ReAct Agent strategy. It is built for developers using Dify who want to integrate external MCP-compatible tools, resources, and prompts.

How to use dify-mcp-client?

Install the plugin from GitHub or from a .difypkg release file via Dify's plugin manager. After installation, add an Agent node in any Dify Chatflow and select "mcpReAct" as the agent strategy. Configure the config_json field with server URLs (SSE or Streamable HTTP) to connect MCP servers.

Key features of dify-mcp-client

  • Converts MCP tools, resources, and prompts into Dify tools.
  • Supports SSE, Streamable HTTP, and multiple MCP servers.
  • Integrates UI-TARS-SDK for GUI automation capabilities.
  • Allows user-configurable maximum loop count for GUI actions.
  • Provides Chatflow test examples and DSL (.yml) imports.

Use cases of dify-mcp-client

  • Connect an arxiv MCP server to let an LLM fetch papers autonomously.
  • Build a Chatflow that uses MCP tools to interact with local or remote services.
  • Automate GUI actions by combining UI-TARS vision with MCP tool calling in a Dify workflow.

FAQ from dify-mcp-client

What transport protocols does dify-mcp-client support?

It supports SSE (Server-Sent Events) and Streamable HTTP transports for MCP servers.

Can I use TypeScript stdio MCP servers with this plugin?

Yes, but only if you use the Docker image with pre-installed Node.js inside the plugin-daemon, or deploy from source code (not via .difypkg). Alternatively, convert stdio servers to Streamable HTTP using mcp-proxy.

Does dify-mcp-client include a human-in-the-loop mechanism?

No, it does not implement human-in-the-loop by default. The README recommends connecting only reliable MCP servers and suggests setting max iterations to 1 or adding a permission-asking phrase in the INSTRUCTION field.

Where is the data stored and processed?

Data is processed within the Dify plugin runtime; configuration (server URLs) is provided via the config_json field in the Agent node. No external database is mentioned.

What are the runtime requirements for UI-TARS integration?

UI-TARS integration is supported only in Dify Plugin's local debug deployment (not via .difypkg). It requires a Hugging Face Inference Endpoint URL and API key, and runs UI-TARS-1.5-7B model. Known limitations include single-monitor support and macOS Retina display resolution issues.

Frequently asked questions

What transport protocols does dify-mcp-client support?

It supports SSE (Server-Sent Events) and Streamable HTTP transports for MCP servers.

Can I use TypeScript stdio MCP servers with this plugin?

Yes, but only if you use the Docker image with pre-installed Node.js inside the plugin-daemon, or deploy from source code (not via .difypkg). Alternatively, convert stdio servers to Streamable HTTP using mcp-proxy.

Does dify-mcp-client include a human-in-the-loop mechanism?

No, it does not implement human-in-the-loop by default. The README recommends connecting only reliable MCP servers and suggests setting max iterations to 1 or adding a permission-asking phrase in the INSTRUCTION field.

Where is the data stored and processed?

Data is processed within the Dify plugin runtime; configuration (server URLs) is provided via the `config_json` field in the Agent node. No external database is mentioned.

What are the runtime requirements for UI-TARS integration?

UI-TARS integration is supported only in Dify Plugin's local debug deployment (not via .difypkg). It requires a Hugging Face Inference Endpoint URL and API key, and runs UI-TARS-1.5-7B model. Known limitations include single-monitor support and macOS Retina display resolution issues.

Comments

Basic information

Category

Developer Tools

License

Apache-2.0

Transports

stdio

Author

3dify-project

More Developer Tools MCP servers

MCP Inspector

modelcontextprotocol

Visual testing tool for MCP servers

10.3K

AptiBuild AI — Career Intelligence

ParklandBuilds

AptiBuild AI MCP Server — career, labor market, and business idea intelligence for AI agents. 11 tools covering real-time FRED labor market signals, BLS wage data (126 occupations), AI-generated app ideas, career paths,

mcp-excalidraw

yctimlin

MCP server and Claude Code skill for Excalidraw — programmatic canvas toolkit to create, edit, and export diagrams via AI agents with real-time canvas sync.

2.1K

Deepwiki MCP Server

regenrek

📖 MCP server for fetch deepwiki.com and get latest knowledge in Cursor and other Code Editors

1.4K

Altronis

sypherin

MCP server + CLI for Altronis — Singapore AI consulting. Ask the Lyra consultant, generate a grant-matched AI transformation plan, pull curated SG AI events/news. Read-only, wraps altronis.sg.