Dify Agent Mcp Sse

Created By
junjiema year ago
Overview

What is Dify Agent Mcp Sse?

Dify Agent Mcp Sse is a plugin that supports MCP (Managed Communication Protocol) tools and agent strategies, enabling function calling and reactive strategies through HTTP with Server-Sent Events (SSE) or Streamable HTTP transport.

How to use Dify Agent Mcp Sse?

To use this plugin, install it via the Dify platform's plugin management page by entering the GitHub repository address. You can configure multiple MCP servers for different transport methods.

Key features of Dify Agent Mcp Sse?

  • Supports function calling and reactive strategies.
  • Configurable MCP servers for various transport methods (SSE and Streamable HTTP).
  • Easy installation via GitHub repository.

Use cases of Dify Agent Mcp Sse?

  1. Integrating various MCP services into applications.
  2. Enabling real-time data fetching and processing through SSE.
  3. Facilitating communication between different tools and services using MCP protocol.

FAQ from Dify Agent Mcp Sse?

  • How to handle errors when installing plugins?

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

  • How to install the offline version?

Use the provided scripting tool to download and repackage the Dify plugin for offline use.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago