Open source MCP hosting - deploy MCP servers to HTTP endpoints for n8n, Dify, Voiceflow, and any MCP client.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"deploystack": {
"url": "https://satellite.deploystack.io/mcp",
"type": "http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Deploy MCP servers from GitHub to HTTP endpoints in 30 seconds. Works with n8n, Dify, Voiceflow, Langflow, Claude Code, Cursor, and any MCP client.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
Enhanced MCP server for GitLab: group projects listing and activity tracking
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for Deploystack and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
🚀 Try it out ·
🌐 Website ·
📚 Documentation ·
Roadmap ·
Discord
Deploy MCP servers from GitHub to HTTP endpoints in 30 seconds. Works with n8n, Dify, Voiceflow, Langflow, Claude Code, Cursor, and any MCP client.
Most MCP servers are stdio-only. But workflow automation platforms need HTTP endpoints.
| Platform | What They Need | The Problem |
|---|---|---|
| n8n | HTTP URLs for MCP Client node | stdio doesn't work |
| Dify | HTTP/SSE endpoints (v1.6+) | No stdio support |
| Voiceflow | Remote MCP endpoints | "Local MCP NOT supported" |
| Langflow | HTTP/SSE for production | Local processes won't scale |
Current workarounds are painful:
mcp-remote requires local Node.js setupAnd for teams, the problems multiply:
.env files.env files into an encrypted vault with automatic injectionnpm install, no process management, no port conflicts