MCP Catalogs
← Homedeploystack screenshot

deploystack

by deploystackio·★ 57·Score 47

DeployStack transforms stdio-only MCP servers into HTTP endpoints for automation platforms.

developer-toolsops-infraai-llm
4
Forks
46
Open issues
this month
Last commit
2d ago
Indexed

Overview

DeployStack is a hosting platform that allows users to deploy MCP servers as HTTP endpoints, solving the limitation where most MCP servers only work via stdio. It enables integration with workflow automation platforms like n8n, Dify, Voiceflow, and Langflow that require HTTP connections. The platform supports deployment directly from GitHub repositories or through a curated catalog of MCP servers, with features like credential management, team access controls, and audit logging.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Workflow automation in n8n using MCP servers as HTTP nodes
you:Team-based MCP server deployment with credential management and access controls
you:Production deployment of MCP servers without DevOps expertise
you:How does DeployStack reduce token consumption?
you:Which MCP clients are compatible with DeployStack?

When to choose this

Choose DeployStack when you need to host MCP servers as HTTP endpoints for integration with workflow tools like n8n, Dify, or Voiceflow, or when you need team management features with RBAC and credential management for MCP servers.

When NOT to choose this

Avoid DeployStack if you only need simple stdio-based MCP servers without HTTP requirements, if you need full control over deployment environment, or if you prefer open-source without any proprietary components.

Tools this server exposes

2 tools extracted from the README
  • discover_mcp_tools

    Find relevant MCP tools from the available servers

  • execute_mcp_tool

    Execute a specific MCP tool from a deployed server

Comparable tools

mcp-remoten8n-mcpself-hosted-docker-mcpmcp-ng

Installation

Installation

Using DeployStack Cloud

  1. Sign up at [cloud.deploystack.io](https://cloud.deploystack.io)
  2. Connect your GitHub account or browse the MCP catalog
  3. Deploy a repository or install from catalog
  4. Configure credentials if needed
  5. Get your HTTP endpoint URL
  6. Add to your MCP client configuration:
{
  "mcpServers": {
    "deploystack": {
      "type": "http",
      "url": "https://satellite.deploystack.io/mcp"
    }
  }
}

Self-Hosting

git clone https://github.com/deploystackio/deploystack
cd deploystack
docker-compose up

See the [Self-Hosting Documentation](https://docs.deploystack.io/self-hosted/quick-start) for detailed instructions.

FAQ

How does DeployStack reduce token consumption?
DeployStack uses a hierarchical router pattern that exposes only 2 meta-tools (discover_mcp_tools and execute_mcp_tool) instead of loading all tools into context, achieving 98% token reduction compared to traditional MCP setups.
Which MCP clients are compatible with DeployStack?
DeployStack works with any MCP client that supports HTTP/SSE transport, including n8n, Dify, Voiceflow, Langflow, Claude Code, Cursor, and custom implementations.

Compare deploystack with

deploystack vs ultimate_mcp_serverdeploystack vs mcp-server-chartdeploystack vs everythingdeploystack vs filesystemdeploystack vs time
GitHub →

Last updated · Auto-generated from public README + GitHub signals.