Dify Plugin Tools Mcp_sse MCP Server

@junjiem

リポジトリ

基本情報

カテゴリ

開発者ツール

トランスポート

stdio

作者

junjiem

投稿者

Junjie.M

Dify Plugin Tools Mcp_sse MCP Server について

概要はまだありません

#dify #mcp#plugin-tools

Dify Plugin Tools Mcp_sse MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "server_name1": {
      "url": "http://127.0.0.1:8000/sse",
      "headers": {},
      "timeout": 5,
      "sse_read_timeout": 300
    },
    "server_name2": {
      "url": "http://127.0.0.1:8001/sse"
    }
  }
}

Dify Plugin Tools Mcp_sse MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

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

よくある質問

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`).

「開発者ツール」の他のコンテンツ

Official Porkbun MCP Server

Porkbun LLC

Official Porkbun MCP server, maintained by Porkbun. Check domain availability and pricing, register, renew and transfer domains, and manage DNS records, nameservers, URL forwarding, glue records, DNSSEC and domain contac

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

UXMachine

UXMachine measures a web page in a real browser and returns verifiable observations, each with its evidence and its limits. It opens the address on desktop (1280×800) and mobile (390×844) and follows the site's own links

FARPY

mangomunchr

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

Yocoolab

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools