概要
What is Dify Plugin Tools Mcp_sse?
Dify Plugin Tools Mcp_sse is a tool-type plugin for Dify 1.0 that fetches and calls tools via the Model Context Protocol (MCP) over HTTP with SSE transport. It allows users to connect any MCP server that supports SSE and use its tools within Dify agents.
How to use Dify Plugin Tools Mcp_sse?
Install the plugin via its GitHub repository on the Dify plugin management page. After installation, configure one or more MCP servers by providing a JSON object with server names, URLs, optional headers, timeouts, and SSE read timeouts. Alternatively, connect to composio’s managed MCP servers.
Key features of Dify Plugin Tools Mcp_sse
- Discovers and calls tools using MCP over HTTP with SSE
- Supports multiple MCP server configurations simultaneously
- Configurable request headers, timeouts, and SSE read timeouts
- Can connect to composio managed MCP servers for quick testing
- Installs via GitHub repository on the Dify platform
Use cases of Dify Plugin Tools Mcp_sse
- Integrating external MCP tools (e.g., web search, data retrieval) into Dify AI agents
- Connecting multiple MCP services from different providers within one Dify workspace
- Testing MCP servers that expose tools via SSE transport before deployment
- Using managed MCP servers from composio when self-hosting is not feasible
FAQ from Dify Plugin Tools Mcp_sse
How to handle errors when installing plugins due to signature verification?
If you see "plugin verification has been enabled, and the plugin you want to install has a bad signature", add FORCE_VERIFYING_SIGNATURE=false to your .env configuration file. This bypasses the signature check for plugins not listed in the Dify Marketplace.
Does the plugin require a specific runtime or dependencies?
The plugin is designed for Dify 1.0 and runs within the Dify plugin system. No additional runtime is mentioned; it connects to MCP servers over HTTP/SSE.
What transport does the plugin use?
It uses HTTP with Server-Sent Events (SSE) transport for the MCP protocol. Each configured server must expose an SSE endpoint (e.g., http://127.0.0.1:8000/sse).
