Make MCP server

What the model can do

Make automation: organisations and teams, scenarios with status, schedule and run counts, a scenario's execution log and incomplete executions, and the names of connections and data stores. Can run, start, stop, replay, rename, trash or restore a scenario, retry or delete incomplete executions, and add, update or delete data store records.

Reads

• makecom_organizationsMake organisations the token's user belongs to, each with its teams (id and name), scenario and active-scenario counts, and plan.
• makecom_teamsTeams in one Make organisation: id, name, active scenarios and type.
• makecom_scenariosScenarios in a Make team, most recently edited first: active or not, paused, invalid, schedule, next run, last edit, folder…
• makecom_scenario_logsA Make scenario's execution log, newest first: when, success, warning or error, duration, operations and credits used, who triggered it…
• makecom_connectionsConnections in a Make team, by name: the app each is for and when it expires.
• makecom_data_storesData stores in a Make team, by name: how many records and how much space they use.
• makecom_incomplete_executionsA Make scenario's incomplete executions (runs Make stored after an error, to retry): id, reason, when, size, attempts…

Acts, when you ask

These change something in Make. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• makecom_run_scenarioRuns one active Make scenario now, optionally with its scenario inputs.
• makecom_start_scenarioActivates one Make scenario so it runs on its schedule or trigger from now on (a scheduled scenario also runs straight away)…
• makecom_stop_scenarioDeactivates one Make scenario, stopping it if it is running; it no longer runs on its schedule or trigger.
• makecom_replay_executionsReplays named executions of one active Make scenario with their original data on the scenario's latest version.
• makecom_update_scenarioRenames one Make scenario and/or moves it to a folder (folder_id null takes it out of its folder).
• makecom_trash_scenariosMoves named Make scenarios of one team to the trash.
• makecom_restore_scenarioRestores one trashed Make scenario (within 30 days of trashing).
• makecom_retry_incomplete_executionsRetries named incomplete executions of one Make scenario with the blueprint from when each failed.
• makecom_delete_incomplete_executionsPermanently deletes named incomplete executions of one Make scenario; the data Make stored to retry them is lost.
• makecom_create_data_store_recordAdds one record to a Make data store, with the fields its data structure defines.
• makecom_update_data_store_recordChanges the given fields of one Make data store record, by key; fields not given are left as they are.
• makecom_delete_data_store_recordsPermanently deletes named records (by key) from one Make data store.

Connect it

First connect Make on Dashboard → Connections, then add Memtro to your client once. The Make tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Make connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which Make scenarios failed this week?
• › Why did the invoice scenario error yesterday?
• › Which scenarios are paused or invalid?
• › Which Make connections expire soon?
• › Retry the incomplete executions of the invoice scenario

Questions

Is this an official Make MCP server?

No. It is Memtro's MCP server with Memtro's Make connector behind it: the connector reads Make through its API with the credentials you connect on Dashboard → Connections, and Make publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Make?

Only when you ask, and only what it has been granted: run a scenario now (spends operations); start (activate) or stop (deactivate) a scenario; replay named executions of a scenario (spends operations); rename a scenario or move it to a folder; move named scenarios to the trash, or restore one; retry named incomplete executions (spends operations); delete named incomplete executions; add or update a data store record; delete named data store records. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server