Make.com MCP Integration: Deploy and Connect MCP Servers to Your Scenarios
Connect Make.com to MCP servers hosted on DeployStack. Deploy your MCP server from a GitHub repository, get an HTTP endpoint, and add it to Make.com's MCP Client module. No local installations, no Docker containers, no infrastructure to manage — just a URL you paste into your scenario.
Make.com's MCP Client module connects to remote MCP servers and loads their tools directly into your scenarios. Most MCP servers on GitHub only support stdio, which means they can't be used with Make.com directly. DeployStack runs your stdio MCP server on managed infrastructure and exposes it as an HTTP endpoint that Make.com can connect to.
Deploy Any MCP Server for Make.com
Point DeployStack at a GitHub repository containing an MCP server. DeployStack detects the runtime (Node.js, Python, Docker), builds it, and gives you a direct endpoint URL with a token. Add that URL to Make.com's MCP Client module and all tools from that server are loaded automatically into your scenario. When you push changes to your repository, DeployStack redeploys automatically — your Make.com scenarios always use the latest version.
Simple Authentication
Each MCP server you deploy gets its own endpoint URL and instance token. In Make.com's MCP Client module, enter your DeployStack endpoint URL and use the token for authentication. One copy-paste and the connection is ready.
Use MCP Tools in Your Scenarios
Once connected, the tools from your MCP server are available as actions in Make.com. Query databases, create GitHub issues, search documentation, process files — any tool your MCP server exposes becomes a module you can wire into your scenarios. Combine MCP tools with Make.com's existing app integrations to build automations that weren't possible before.
Track What Your Scenarios Are Calling
See which MCP tools your Make.com scenarios call, how often, and whether they succeed or fail. DeployStack's observability dashboard logs every tool interaction, so you can debug failing scenarios and understand which MCP servers your automations depend on.
Your Make.com account is now connected to your DeployStack MCP server. Add the MCP Client module to any scenario, enter your endpoint URL, and Make.com loads the available tools automatically. Select the tool you need and configure the inputs — it works like any other Make.com module.
You can connect multiple MCP servers to the same scenario or across different scenarios — each gets its own endpoint and token.
Need more MCP servers for your scenarios? Browse the DeployStack catalog for popular servers or deploy your own from any GitHub repository.