MCP Make.com Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAKE_ZONE | No | API zone: eu1, eu2, us1, us2 (default: eu1) | eu1 |
| MAKE_API_TOKEN | Yes | Your Make.com API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_scenariosC | List all scenarios for a team or organization |
| get_scenarioC | Get details of a specific scenario |
| create_scenarioC | Create a new scenario with a blueprint. The blueprint defines the workflow modules and their connections. |
| update_scenarioC | Update an existing scenario (name, blueprint, scheduling, folder) |
| delete_scenarioC | Delete a scenario permanently |
| activate_scenarioB | Activate a scenario so it can run |
| deactivate_scenarioC | Deactivate a scenario to stop it from running |
| run_scenarioB | Run a scenario immediately. Scenario must be active and set to on-demand scheduling. |
| clone_scenarioC | Clone/duplicate a scenario |
| get_scenario_blueprintC | Get the full blueprint (flow definition) of a scenario |
| get_scenario_logsC | Get execution logs for a scenario |
| list_connectionsB | List all connections (API credentials) for a team |
| list_hooksB | List all webhooks for a team |
| list_data_storesC | List all data stores for a team |
| get_data_storeC | Get details of a data store |
| create_data_storeD | Create a new data store |
| list_data_store_recordsC | List records in a data store |
| create_data_store_recordC | Create a record in a data store |
| list_teamsC | List all teams in an organization |
| list_organizationsC | List all organizations the user has access to |
| get_current_userB | Get information about the authenticated user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action (scenario lifecycle, data stores, teams, orgs, user, connections, hooks). The scenario tools are clearly differentiated by verb: get, list, create, update, delete, activate, deactivate, run, clone, get_blueprint, get_logs. No two tools appear to do the same thing.
All tool names use snake_case with a consistent verb_noun pattern (e.g., list_scenarios, create_scenario, get_data_store). There are no mixed conventions or vague verbs. The pattern extends to compound resources like create_data_store_record and list_data_store_records.
21 tools is on the heavy side for the server's scope, falling into the 16-25 borderline range. While most tools earn their place by covering distinct operations, the set could likely be consolidated without losing functionality. The count feels somewhat inflated for the core scenario and data store management tasks.
Scenario management is comprehensive (full CRUD plus activate, deactivate, run, clone, blueprint, logs). However, notable gaps exist: data stores and records lack update/delete operations, and connections and hooks are only listable with no create, update, or delete. These missing lifecycle operations will limit agents needing full management.