You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ This plugin includes [UI-TARS SDK](https://github.com/bytedance/UI-TARS-desktop/
48
48
>
49
49
> Normal difypkg install doesn't work. Because UI-TARS require OS native API, yet Dify plugin env is Linux docker container.
50
50
>
51
-
> I'm thinking alternative solusion via HTTP Streamable MCP.
51
+
> I'm thinking alternative solusion via Streamable HTTP MCP.
52
52
### Key Features
53
53
-**On-demand GUI automation**: UI-TARS is called only when needed, reducing token consumption
54
54
-**Life-time control**: Set maximum loop count per task to prevent runaway automation
@@ -161,9 +161,9 @@ MCP Agent Plugin node require config_json like this to command or URL to connect
161
161
> [!WARNING]
162
162
> - Each server's port number should be different, like 8080, 8008, ...
163
163
> - If you want to use stdio mcp server, there are 3 ways.
164
-
> 1. Convert it to SSE mcp server https://github.com/3dify-project/dify-mcp-client/edit/main/README.md#how-to-convert-stdio-mcp-server-into-sse-mcp-server
164
+
> 1. Convert it to Streamable HTTP mcp server using mcp-proxy https://github.com/sparfenyuk/mcp-proxy?tab=readme-ov-file#1-stdio-to-ssestreamablehttp
165
165
> 2. Deploy with source code (**NOT** by .difypkg or GitHub reposity name install) https://github.com/3dify-project/dify-mcp-client/edit/main/README.md#-how-to-develop-and-deploy-plugin
0 commit comments