Make.com MCP server setup guide

How to Set Up and Use the Make.com MCP Server

This guide explains step by step how to install, configure, and run the Make.com MCP server so you can expose tools and data sources to model context protocol (MCP) clients.

What the Make.com MCP Server Does

The Make.com MCP server is a TypeScript implementation of the Model Context Protocol. It acts as a bridge between your tools or data sources and any compatible MCP client.

With this server you can:

  • Expose tools via the MCP protocol.
  • Serve prompts and resources to clients.
  • Run locally for development or in Docker for production.
  • Manage configuration with JSON or environment variables.

The server is open source and available on GitHub, but this article focuses on how to install and configure it for practical use.

Prerequisites for the Make.com MCP Server

Before you install and run the server, make sure you have the following in place:

  • Node.js (LTS version recommended).
  • npm or another Node package manager.
  • Basic command-line knowledge.
  • Docker, if you plan to use the container image.

You should also understand the basics of MCP clients and servers, including how tools, prompts, and resources are defined.

Install the Make.com MCP Server with npm

You can install the Make.com MCP server as a Node package and run it from your local environment.

Step 1: Install the package

  1. Open your terminal.
  2. Run a global or local installation command, for example:
    • npm install @makecom/mcp-server
  3. Wait for the installation to finish without errors.

After installation, the server binary will be available in your node_modules or globally, depending on how you installed it.

Step 2: Create a configuration file

The Make.com MCP server reads configuration from a JSON file. At minimum, you should define:

  • Server metadata (name, version).
  • Tools and their handlers.
  • Optional prompts.
  • Optional resources.

Create a file such as mcp.config.json in your project. Inside, declare your tools and any prompts or resources the server should expose.

Step 3: Run the Make.com MCP server locally

  1. From your project directory, run a command similar to:
    • npx mcp-server --config ./mcp.config.json
  2. Watch the terminal output to confirm the server started successfully.
  3. Note any port, socket, or stdio details required by your MCP client.

Once running, you can connect an MCP client by referencing the command, arguments, and configuration path in the client settings.

Use the Make.com MCP Server Docker Image

You can also run the Make.com MCP server using a Docker image, which is convenient for isolated or production environments.

Step 1: Pull the Docker image

  1. Open your terminal.
  2. Run:
    • docker pull makecom/mcp-server
  3. Wait until the image is successfully downloaded.

Step 2: Prepare configuration for Docker

Create a configuration file on your host machine, as described earlier. You will mount this file into the container so the server can load it.

For example, store it at /path/to/mcp.config.json on your local system.

Step 3: Run the container

  1. Execute a command such as:
    • docker run --rm -v /path/to/mcp.config.json:/app/mcp.config.json makecom/mcp-server --config /app/mcp.config.json
  2. Check the container logs to ensure the server started correctly.
  3. Configure your MCP client to talk to the server through the Docker runtime or any exposed socket.

Configure the Make.com MCP Server

The Make.com MCP server is controlled primarily by its configuration file. This file declares what the server can do and how it interacts with clients.

Core configuration sections

A typical configuration includes these sections:

  • Server information — name, description, and version.
  • Tools — each tool with its name, description, schema, and handler command.
  • Prompts — reusable prompt templates that clients can call.
  • Resources — data sources or read-only information the server exposes.

Defining tools in Make.com MCP configuration

Tools are the heart of any Make.com MCP server deployment. When defining a tool, specify at least:

  • A unique tool name.
  • A human-readable description.
  • Input parameters and types.
  • The handler process or script that executes the logic.

The server passes tool calls from the client to the handler and returns the output in MCP-compliant format.

Managing environment variables

You can keep sensitive values like API keys outside the JSON file by using environment variables. Reference them in the tool handlers or scripts rather than hardcoding them in configuration.

Connect MCP Clients to the Make.com MCP Server

Once the Make.com MCP server is running, you need to connect one or more MCP clients so they can access tools and resources.

General client setup steps

  1. Locate the MCP settings in your preferred client.
  2. Add a new server entry that points to your local command or Docker container.
  3. Specify the command (or Docker wrapper), arguments, and any required environment variables.
  4. Save the configuration and restart the client if necessary.

After the client connects, it should list the tools, prompts, and resources provided by your server.

Troubleshooting the Make.com MCP Server

If the Make.com MCP server does not work as expected, follow these checks:

  • Configuration validation: Ensure the JSON configuration is valid and keys are spelled correctly.
  • Logs and errors: Review terminal output or container logs for stack traces or validation messages.
  • Client configuration: Confirm the client uses the correct command, path, and protocol.
  • Permissions: Verify that your user and Docker container can access configuration files and scripts.

You can also confirm behavior by calling a simple tool that returns static data before moving to more complex workflows.

Where to Learn More About the Make.com MCP Server

To deepen your understanding of the Make.com MCP server implementation, configuration options, and example setups, consult the official documentation:

For broader automation strategy, integration design, and consulting around tools that interact with this server, you can also visit Consultevo for additional resources.

By following the steps in this article, you can successfully install, configure, and operate the Make.com MCP server in local and containerized environments, then connect it to MCP clients to provide powerful tools, prompts, and resources.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help

Leave a Comment

Your email address will not be published. Required fields are marked *