DeployStack MCP Server

Open source MCP hosting - deploy MCP servers to HTTP endpoints for n8n, Dify, Voiceflow, and any MCP client. Exposed over MCP by the deploystack mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Deploy MCP servers from GitHub to HTTP endpoints in 30 seconds. Works with n8n, Dify, Voiceflow, Langflow, Claude Code, Cursor, and any MCP client.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• mcp — remote requires local Node.js setup
• Client — ready MCP hosting**: Deploy MCP servers for client projects without managing infrastructure
• White — label ready**: Team isolation keeps client data separate
• One — click installation
• Pre — configured and tested
• Auto — deploy on git push
• discover_mcp_tools — find relevant tools
• execute_mcp_tool — run the tool you need
• Result — 1,372 tokens instead of 75,000
• Platform — cloud.deploystack.io
• Documentation — docs.deploystack.io
• GitHub — github.com/deploystackio/deploystack

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch DeployStack.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the deploystack mcp server does with a few real requests.

When to reach for it

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. DeployStack's toolset — mcp, Client, White and 11 more — is a fair guide to whether it matches your workflow. It is maintained by deploystackio; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.