Skip to main content
TS
ESEN
Connectors

Make

Your Make automations, within reach of the agent

Run and manage your Make automations from the chat

Official Make MCP: run your scenarios and review your automation setup over OAuth — no API key to paste.

Make is the visual automation platform many businesses use to connect their apps without writing code: a scenario watches for something happening — a new order, a form submission, a new row in a spreadsheet — and then carries out the steps you set up across your tools. The official Make MCP server lets your agent trigger those scenarios and manage your automation setup directly — no API key pasted into TerminalSync, just your own Make account login.

Ask "Run my 'New order' scenario right now" and the agent triggers it and brings back the result. Ask "Show me all my Make scenarios and which ones are active" and you get the full picture without opening Make. It's built for running your automations on demand and reviewing what's configured: scenarios, the connections they use, the webhooks that feed them and the data stores behind them.

One thing to know, straight from Make's docs: scenario run tools are available to all plans, while the management tools (viewing and changing scenarios, connections, webhooks, data stores, teams and organizations) are available to paid plans.

What you can ask

  • "Run my 'New order' scenario right now."
  • "Show me all my Make scenarios and which ones are active."
  • "List the connections my scenarios use."
  • "Show me the webhooks my scenarios receive data through."
  • "Which teams and organizations do I belong to in Make?"
  • "Add a data store my scenarios can use."

Before anything that changes your setup — running a scenario or modifying one — your agent asks you to confirm first.

How you connect

This connector doesn't ask you to paste an API key. It uses your own Make account login:

  1. Enable the connector in TerminalSync.
  2. The mcp-remote bridge opens Make's login in your browser.
  3. Choose your organization and the access you want to grant — Make's docs put it plainly: "You select scopes when you connect Make MCP server to an MCP client." The connector can only see and do what those scopes allow. Make's setup guide is at developers.make.com.

Honest note: this is a server hosted by Make (https://mcp.make.com/v2), not something that runs on your computer. Scenarios run inside your Make account, and what the agent can see or change is bounded by the scopes you approve and the permissions your account already has.

Add to TS

We open the app and set it up in Claude Code (and your other Macs).

View Make →
Don't have TS yet?Download →

What you can ask

  • Run your scenario right now

    Starts the Make scenario you need and brings its result back to the chat.

  • Your automations at a glance

    Lists every Make scenario and which are active, so you see the whole map without opening Make.

  • Audit of your scenarios' connections

    Lists the connections (other apps' accounts) your scenarios use to spot risky ones.

  • New data store for your scenarios

    Creates a Make data store your scenarios can use, confirming first.

See all use cases →

How it works with TS

Set up the connector once on one machine. TS keeps your claude_desktop_config.json encrypted in your Drive, so on any other machine where you open Claude Code, the connector is already there.