MCP HTTP SSE
A plugin that allows Dify to connect to multiple MCP (Model Control Protocol) servers using HTTP with Server-Sent Events transport, supporting custom configurations for URLs, headers, and timeouts.
What is MCP HTTP SSE?
MCP HTTP SSE is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to plugin that allows dify to connect to multiple mcp (model control protocol) servers using http with server-sent events transport, supporting custom configurations for urls, headers, and timeouts.
A plugin that allows Dify to connect to multiple MCP (Model Control Protocol) servers using HTTP with Server-Sent Events transport, supporting custom configurations for URLs, headers, and timeouts.
This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- A plugin that allows Dify to connect to multiple MCP (Model
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx mcp-http-with-sse-transport-toolsConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use MCP HTTP SSE
The MCP HTTP with SSE Transport Tools plugin connects the Dify AI platform to external MCP servers using HTTP with Server-Sent Events or Streamable HTTP transport, enabling Dify workflows and agents to call tools hosted on any SSE-compatible MCP server. It supports configuring multiple MCP server endpoints simultaneously with per-server settings for custom headers, request timeouts, and SSE read timeouts. Teams building Dify agents use it to access tools from managed MCP platforms like Composio, Zapier MCP, and MCP.so, or to bridge self-hosted MCP servers into their Dify workflows.
Prerequisites
- A running Dify 1.0+ instance (self-hosted or Dify Cloud)
- Access to Dify's plugin management interface with permission to install plugins
- One or more MCP servers accessible via HTTP/SSE endpoints
- For Dify self-hosted instances: FORCE_VERIFYING_SIGNATURE=false in .env if signature verification fails
Open Dify Plugin Management
In your Dify instance, navigate to the Plugin Management page. This is where you install third-party plugins that extend Dify's tool capabilities.
Install from GitHub
Select the GitHub installation method and enter the repository URL. Then choose the version and the appropriate package file to install.
# Repository URL to enter in Dify plugin manager:
https://github.com/junjiem/dify-plugin-tools-mcp_sse(If needed) Disable signature verification
If Dify shows a signature verification error during installation, add the following to your Dify .env file and restart Dify before retrying the installation.
FORCE_VERIFYING_SIGNATURE=falseConfigure your MCP server endpoints
After installation, configure the plugin with your MCP server connection details. Each server entry specifies a transport type, URL, optional headers, and timeouts.
{
"my_mcp_server": {
"transport": "sse",
"url": "http://127.0.0.1:8000/sse",
"timeout": 50,
"sse_read_timeout": 300
},
"zapier_mcp": {
"transport": "sse",
"url": "https://actions.zapier.com/mcp/sk-your-key/sse"
}
}Use MCP tools in Dify workflows or agents
The plugin discovers available tools from all configured MCP servers and makes them available in Dify's tool selector. Add them to your workflow nodes or agent tool lists like any other Dify tool.
MCP HTTP SSE Examples
MCP servers configuration
Example configuration for connecting to a local MCP server via SSE and a managed Zapier MCP endpoint with custom headers.
{
"local_server": {
"transport": "sse",
"url": "http://127.0.0.1:8000/sse",
"timeout": 50,
"sse_read_timeout": 300
},
"zapier": {
"transport": "sse",
"url": "https://actions.zapier.com/mcp/sk-your-api-key/sse",
"headers": {
"Authorization": "Bearer your-token"
},
"timeout": 60
}
}Prompts to try
Example Dify agent prompts that would invoke tools discovered through the MCP SSE plugin.
- "Use the connected MCP tools to search for recent news about AI"
- "Send an email via the Zapier MCP integration to my team with a project status update"
- "List all available tools from the connected MCP servers"
- "Query my custom MCP server to retrieve data from the products database"
- "Trigger a Zapier automation to create a Slack message with this content"Troubleshooting MCP HTTP SSE
Plugin installation fails with signature verification error
Add FORCE_VERIFYING_SIGNATURE=false to your Dify .env file, then restart Dify and retry the installation. This is a known issue with GitHub-installed Dify plugins that are not in the official marketplace.
SSE connections time out or drop when calling long-running MCP tools
Increase the sse_read_timeout value in your server configuration (e.g., set to 600 for 10 minutes). Also check your Nginx configuration — if Dify runs behind Nginx, set NGINX_KEEPALIVE_TIMEOUT=650 or higher to prevent the proxy from closing long-lived SSE connections.
MCP tools are not appearing in Dify's tool selector after configuration
Verify the MCP server URL is reachable from the Dify server (not just your browser). Use curl to test the SSE endpoint: curl -N http://your-mcp-server/sse. Check that the transport field in your config matches what the server actually supports (sse vs streamable_http).
Frequently Asked Questions about MCP HTTP SSE
What is MCP HTTP SSE?
MCP HTTP SSE is a Model Context Protocol (MCP) server that plugin that allows dify to connect to multiple mcp (model control protocol) servers using http with server-sent events transport, supporting custom configurations for urls, headers, and timeouts. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install MCP HTTP SSE?
Follow the installation instructions on the MCP HTTP SSE GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with MCP HTTP SSE?
MCP HTTP SSE works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is MCP HTTP SSE free to use?
Yes, MCP HTTP SSE is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
MCP HTTP SSE Alternatives — Similar Developer Tools Servers
Looking for alternatives to MCP HTTP SSE? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.
Ecc
★ 188.2kThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Javaguide
★ 155.8kJava 面试 & 后端通用面试指南，覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Gemini CLI
★ 104.5kA secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in
Awesome MCP Servers
★ 87.3k⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.
MCP Servers
★ 86.0kModel Context Protocol Servers
CC Switch
★ 77.5kA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
Browse More Developer Tools MCP Servers
Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up MCP HTTP SSE in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use MCP HTTP SSE?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.