Dify Plugin Tools Mcp_sse

Created By
junjiema year ago
Overview

what is Dify Plugin Tools MCP SSE?

Dify Plugin Tools MCP SSE is a tool designed to fetch and call tools using the MCP protocol through HTTP with SSE transport. It allows users to manage multiple MCP servers and facilitates the installation of plugins via GitHub.

how to use Dify Plugin Tools MCP SSE?

To use the tool, configure your MCP servers in the provided JSON format, and install plugins by entering the GitHub repository address on the Dify platform's plugin management page.

key features of Dify Plugin Tools MCP SSE?

  • Supports multiple MCP services configuration.
  • Allows installation of plugins directly from GitHub.
  • Provides error handling solutions for plugin installation issues.

use cases of Dify Plugin Tools MCP SSE?

  1. Managing and calling various tools through MCP protocol.
  2. Installing and managing plugins for enhanced functionality.
  3. Connecting to managed MCP servers for testing and development.

FAQ from Dify Plugin Tools MCP SSE?

  • How to handle errors when installing plugins?

If you encounter a bad signature error, add FORCE_VERIFYING_SIGNATURE=false to your .env configuration file to allow installation of unverified plugins.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
junjiem
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago