Open source MCP hosting - deploy MCP servers to HTTP endpoints for n8n, Dify, Voiceflow, and any MCP client.
{
"mcpServers": {
"deploystack": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Open source MCP hosting - deploy MCP servers to HTTP endpoints for n8n, Dify, Voiceflow, and any MCP client.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
AGPL-3.0. View license →
Is it maintained?
Last commit 9 days ago. 55 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
MCPSDK.dev(ToolSDK.ai)'s Awesome MCP Servers and Packages Registry and Database with Structured JSON configurations. Supports OAuth2.1, DCR...
The full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.
Prismer Cloud
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
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