Dify MCP Server

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

Local serverstdioPython

What is the Dify MCP server?

MCP Client as an Agent Strategy Plugin. Support GUI operation via UI-TARS-SDK. The dify mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

This plugin includes UI-TARS SDK integration for GUI automation capabilities.

  • On-demand GUI automation — UI-TARS is called only when needed, reducing token consumption
  • Life-time control — Set maximum loop count per task to prevent runaway automation

Its toolset

Everything the assistant can do here goes through one of these:

  • Life — time control**: Set maximum loop count per task to prevent runaway automation
  • Default — 10 iterations
  • User — configurable maximum via ui_tars_max_life_time_count
  • Reference — The Reference tool exposed by this server

Adding it to your client

mcp-simple-arxiv on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 3 environment variables: CMD_NAME_OR_PATH, REMOTE_INSTALL_HOST, REMOTE_INSTALL_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dify's toolset — Life, Default, User and 1 more — is a fair guide to whether it matches your workflow. It is maintained by 3dify-project; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the dify mcp server does with a few real requests.

Available tools

ToolWhat it does
Lifetime control**: Set maximum loop count per task to prevent runaway automation
Default10 iterations
Userconfigurable maximum via ui_tars_max_life_time_count
ReferenceThe Reference tool exposed by this server.

How to install the Dify MCP server

{
  "mcpServers": {
    "SERVER_NAME": {
       "command": CMD_NAME_OR_PATH 
       "args": {VALUE1, VALUE2}
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CMD_NAME_OR_PATHFilesystem location the server is allowed to use.Optional
REMOTE_INSTALL_HOSTEndpoint or connection string the server talks to.Optional
REMOTE_INSTALL_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Dify to Life.
  • Use Dify to Default.
  • Use Dify to User.

Frequently asked questions

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