Make

Agents can work with your Make automations — looking up your organization and teams, and running the scenarios you have made available to MCP. If your team already wires apps together in Make, this lets an agent use that work instead of rebuilding it.

Note: Make appears in the catalog on every instance; no experimental setting is needed.

Before you connect

  • A Make account.
  • Access to the scenarios you want agents to use, with those scenarios exposed to MCP in Make.

If you plan to use a token instead of browser sign-in, you also need:

  • A Make API token with the mcp:use scope, plus any extra scopes your chosen scenarios require.
  • Your organization's zone host, such as eu2.make.com. Make shows it in its MCP client setup instructions.

Connect Make

  1. Open Connectors and select Make.
  2. Read the access line above the main button. It says who the connection belongs to and which agents can use it. Select Change to pick a different identity, narrow the agents, or choose the token method.
  3. Connect with one of these methods:
    • Sign in with Make — select Continue to sign in and complete browser sign-in. ThinkingMach registers its client automatically, so there is nothing to set up in a developer console.
    • Use an MCP token — enter your Make zone host (for example eu2.make.com) and paste the token into Your Make key.

With a token, ThinkingMach builds the server address as https://<zone>/mcp. The zone must be a make.com host. The token is stored as a secret and sent as a Bearer header. Never put it in a URL.

Choose access

Reach depends on what Make allows the connected identity: which scenarios are exposed to MCP and, with a token, which scopes the token carries. Only give a token the scopes your scenarios actually need.

A scenario can do anything it was built to do — send messages, update records, move money between systems. When an agent runs one, those effects are real. ThinkingMach lists each action Make exposes and starts them as Allowed, so review the list on the Permissions tab:

  • Keep reads, such as organization and team lookups, Allowed.
  • Set anything that runs a scenario or changes data to Ask first, or Off until you need it.

See Set action permissions.

Try it

Start with a read:

Use Make to list the organization and teams this connection can see. Do not run any scenarios.

Compare the result with what you see in Make. That confirms the credential without triggering an automation.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Problem Likely cause Fix
The zone host is refused It is not a make.com host, or it includes https:// or a path Enter just the host, such as eu2.make.com
The token is rejected It is missing mcp:use, was revoked, or belongs to another zone Create a token with mcp:use in the right organization and reconnect
A scenario does not appear It is not exposed to MCP, or the token lacks a scope it needs Expose the scenario in Make, or add the scope to the token
A scenario ran unexpectedly Its action was Allowed Set it to Ask first on the Permissions tab
Needs attention The grant or token was revoked Select Reconnect

Limitations: one Make identity per connection. Which scenarios are available is decided in Make, not in ThinkingMach.

Sources