Make Integration Debugger MCP Server

Make Integration Debugger MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Aids in debugging integration issues between the Make automation platform and Claude Desktop using the Model Context Protocol (MCP).

What you get

Próbowałem stworzyć integrację między platformą automatyzacji Make (dawniej Integromat) a Claude Desktop za pomocą protokołu MCP (Model Context Protocol). Mimo wielu podejść i modyfikacji, nie udało się ustanowić poprawnego połączenia.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: MAKE_API_TOKEN, PORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the make integration debugger mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by 3rzy; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Make Integration Debugger's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.