DeployStack - Open Source MCP Hosting Platform

🚀 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.

The Problem

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 setup
• Docker containers need DevOps expertise
• DIY hosting (Fly.io, Railway) takes hours

And for teams, the problems multiply:

• Credentials scattered across Slack DMs and .env files
• No visibility into who uses which tools
• Onboarding new developers takes hours
• When someone leaves, good luck rotating all those API keys

Who DeployStack Is For

For AI Automation Builders

• n8n, Dify, Voiceflow, Langflow users: Get HTTP endpoints for MCP servers - no more stdio limitations
• No DevOps required: Skip the Docker containers and mcp-remote setup
• Deploy your custom MCP servers: Point at a GitHub repo, get a URL in 30 seconds
• Focus on workflows: Build automations, not infrastructure

For Automation Agencies

• Client-ready MCP hosting: Deploy MCP servers for client projects without managing infrastructure
• White-label ready: Team isolation keeps client data separate
• Scale without ops burden: Add more MCP servers without adding DevOps headcount
• Credential management: Secure vault for all your clients' API keys

For Platform / DevOps Teams

• End credential chaos: Move API keys from Slack DMs and .env files into an encrypted vault with automatic injection
• Control MCP access: Role-based permissions determine who can use which MCP servers and tools
• Prevent data exposure: Team isolation and audit logging show exactly what tools accessed what data
• Centralize configuration: One source of truth instead of N developers × M configurations

For Developers

• Zero setup: Add one URL to your MCP client, get access to all team MCP tools instantly
• No local installs: No npm install, no process management, no port conflicts
• Just works: Same configuration everywhere - no more "works on my machine" debugging
• Focus on code: Security and credentials are handled for you

For Engineering Managers

• 1-click team onboarding: New developer? They're productive with MCP tools in minutes, not hours
• Reduce AI costs: 98% token reduction means lower API bills and better LLM performance
• Full visibility: See which tools your team uses, how often, and what they access
• Offboarding safety: When someone leaves, revoke access instantly - no credential rotation nightmare

The Solution

DeployStack hosts MCP servers as HTTP endpoints. Two ways to use it:

Deploy from GitHub

Point DeployStack at any GitHub repo with an MCP server: