dify-plugin-tools _sse

This MCP server implements an HTTP interface for MCP using SSE (Server-Sent Events) or Streamable HTTP transport. It lets you discover and call tools defined by the MCP protocol over HTTP streams, enabling you to fetch tool metadata, invoke tool actions, and receive streaming results where supported. By default, the server operates with SSE, but you can configure it to use the streamable_http transport for more flexible streaming behavior. Use the provided MCP configuration to point to one or more upstream MCP endpoints and then query or invoke tools through the MCP protocol as you would with any other MCP-enabled service. The example configuration shows how to enable multiple MCP services within a single instance; you can add more server_name entries to connect to additional endpoints as needed.

Prerequisites:

• Node.js and npm installed on the host
• Access to the MCP service endpoints you want to connect to (SSE or Streamable HTTP endpoints)

Installation steps:

1. Clone the repository: git clone https://github.com/junjiem/dify-plugin-tools-mcp_sse.git cd dify-plugin-tools-mcp_sse

2. Install dependencies: npm install

3. Configure MCP servers:

   • Edit the configuration file or environment to include your mcpServers settings. Example (config.json or equivalent): { "mcpServers": { "server_name1": { "transport": "sse", "url": "http://127.0.0.1:8000/sse", "headers": {}, "timeout": 50, "sse_read_timeout": 50 } } }
   • If the project expects environment-based configuration, set the corresponding ENV vars as documented by the repository (e.g., MCP_URL, MCP_TRANSPORT, etc.).

4. Run the server:

   • If the project provides a start script, use: npm run start
   • Otherwise, start directly with Node (adjust path as needed): node dist/server.js

5. Verify:

   • Open the configured URL or use your MCP client to connect to the server and list tools, then execute a test call to ensure MCP interactions work as expected.

Tips and common considerations:

• The default transport is SSE; if your environment requires streaming, you can switch to streamable_http by updating the transport field in the mcpServers configuration.
• Ensure network access from the MCP plugin host to the configured SSE/Streamable HTTP endpoints. Firewalls or proxies may require header adjustments.
• If you encounter timeouts, adjust timeout and sse_read_timeout settings in the MCP server configuration according to your network latency.
• Some MCP endpoints may require custom headers for authentication. Populate the headers object in the configuration accordingly.
• When hosting multiple MCP services, you can add additional entries under mcpServers to manage each endpoint independently.
• Review any security implications of connecting to external MCP servers and manage credentials securely (do not commit secrets in code).