Make.com MCP Connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAKE_ZONE | No | Region (zone) of your Make instance. E.g., eu1, eu2, us1, us2. Default is eu1. | eu1 |
| MAKE_ORG_ID | No | Default organization ID (optional). | |
| MAKE_TEAM_ID | No | Default team ID (optional). | |
| MAKE_API_BASE | No | Full override of the base API URL (optional). | |
| MAKE_API_TOKEN | Yes | API token for Make.com. Created in Make: Profile → API / MCP access → Add token. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| make_list_organizationsA | List all Make.com organizations the API token has access to. Returns id + name. Use this first if you don't know the organization_id. |
| make_list_teamsA | List teams inside a Make.com organization (id + name). teamId is required by make_list_scenarios. If organization_id is omitted, the configured one is used, or the single org is auto-selected. |
| make_list_scenariosA | List Make.com scenarios (automations) for a team or organization. Provide team_id OR organization_id (falls back to the configured ones, or the single org). Set active_only=true to return only active scenarios. Results are capped (default 500); 'capped' tells you if more exist. |
| make_get_scenarioA | Get full details of a single Make.com scenario by its ID (status, scheduling, team, description, etc.). |
| make_run_scenarioA | Run a Make.com scenario on demand (right now). By default waits for the run to finish and returns the result (Make waits up to ~40s); set wait=false to trigger and return the executionId immediately without waiting. 'data' is optional input passed to the scenario (only relevant if it starts with a trigger that accepts input). NOTE: the scenario must be ACTIVE — Make returns HTTP 422 'Scenario is not activated' for an inactive scenario; if needed, activate it first with make_start_scenario. |
| make_start_scenarioC | Activate (turn ON / schedule) a Make.com scenario so it runs on its schedule or trigger. |
| make_stop_scenarioA | Deactivate (turn OFF) a Make.com scenario so it stops running on its schedule/trigger. |
| make_list_executionsA | List the execution history (logs) of a Make.com scenario, newest first. Shows whether runs succeeded/failed and when. Optionally filter by status (1=success, 2=warning, 3=error). |
| make_get_executionA | Get full details of a single scenario execution/log (status, operations, duration, error info) by scenario_id + execution_id (from make_list_executions). |
| make_open_in_browserA | Open a Make.com URL (e.g. a scenario editor link) in the default browser on the user's computer. |
| make_list_data_storesA | List Make.com data stores (Make's built-in lightweight database) for a team. team_id falls back to the configured team or the only team. Returns id, name and record info. |
| make_get_recordsA | List the records in a Make.com data store. Each record has a 'key' and a 'data' object. Results are capped (default 100). |
| make_add_recordA | Add a new record to a Make.com data store. 'data' is an object with the record's fields (must match the data store's structure). 'key' is optional — Make auto-generates one if omitted. |
| make_update_recordA | Replace an existing record in a Make.com data store, identified by its key. 'data' is the full new object for the record (it REPLACES the record). |
| make_delete_recordA | Delete SPECIFIC record(s) from a Make.com data store by key(s). Pass 'keys' as an array of the record keys to delete — ONLY those are removed. Deleting ALL records is intentionally NOT supported here, for safety. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yuli-tonkin-bg/make-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server