Make MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAKE_ZONE | Yes | Region (zone) of your Make instance, e.g., eu1, us1, etc. 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 base URL (optional) | |
| MAKE_API_TOKEN | Yes | API token for Make.com (required) |
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). |
| make_start_scenarioA | 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. |
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-v1.1.1'
If you have feedback or need assistance with the MCP directory API, please join our Discord server