Make MCP Server

How to use

You will interact with the MCP server through your preferred MCP client. The server exposes tooling to run on-demand scenarios, inspect and manage scenarios, view execution logs, and configure scenario interfaces. Use the provided tools to trigger scenarios with the appropriate inputs, inspect results, and manage the lifecycle of your scenarios (create, update, clone, activate, deactivate, and delete). To get started, install the server components, configure your client with the required API keys and zone, then connect your AI assistant to call the available tools like run_scenario_{id}, list_scenarios, get_scenario, and get_logs.

Key capabilities include the ability to:
- Trigger on-demand Make scenarios via run_scenario_{id} and receive structured outputs
- List and view scenarios with status, details, and scheduling
- Create, clone, update, and delete scenarios, including blueprint management and interface configuration
- Activate or deactivate scenarios to control scheduled execution
- Retrieve incomplete execution logs for debugging and DLQ insights.

How to install

Prerequisites are Node.js and access to your MCP client. You will configure MCP server connections in your client using either a local (stdio) runtime or a npx-based approach, as shown below.

{
  "mcpServers": {
    "make": {
      "command": "node",
      "args": ["/path/to/make-mcp-server/build/index.js"],
      "env": {
        "MAKE_API_KEY": "<your-api-key>",
        "MAKE_ZONE": "<your-zone>",
        "MAKE_TEAM": "<your-team-id>"
      }
    }
  }
}

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": ["-y", "@makehq/mcp-server"],
      "env": {
        "MAKE_API_KEY": "<your-api-key>",
        "MAKE_ZONE": "<your-zone>",
        "MAKE_TEAM": "<your-team-id>"
      }
    }
  }
}

Additional setup and notes

Configure the following environment variables in your client or deployment environment where the MCP server runs. The API key grants access to Make scenarios, and the zone and team identify your Make organization.

Environment variables to configure: - MAKE_API_KEY: Your Make API key with appropriate scopes - MAKE_ZONE: Your organization’s zone (for example, us2.make.com or eu1.make.com) - MAKE_TEAM: Your team identifier, typically found in your team URL

Security and access considerations

Treat API keys as sensitive credentials. Use least-privilege scopes where possible, and rotate keys periodically. When running locally or in a team environment, ensure access to the MCP client and server is restricted to authorized users only.

Troubleshooting

If you encounter connectivity or authorization issues, verify that your MAKE_API_KEY, MAKE_ZONE, and MAKE_TEAM values are correct and that the MCP server process has access to those environment variables. Check that the server process is running and that your MCP client points to the correct local runtime or MCP URL as configured.

Examples and troubleshooting tips

Common workflows include listing scenarios to confirm available options, retrieving a scenario’s details before invoking it, then running a specific on-demand scenario with the required input parameters. Use get_logs to inspect incomplete executions if a run does not complete as expected.

Maintenance and roadmap

This fork adds full scenario lifecycle management to the base MCP server. Planned future work includes further connection management, data store operations, and webhook configuration.

License

License information is defined in the upstream project and should be consulted for usage terms and restrictions.

run_scenario_{id}

Execute an on-demand scenario by its identifier with the required input parameters and receive structured results suitable for AI consumption.

list_scenarios

List all scenarios with optional filtering by type or status to understand what is available.

get_scenario

Retrieve full details of a specific scenario, including its status and scheduling.

create_scenario

Create a new scenario, optionally with blueprint and scheduling definitions.

update_scenario

Update an existing scenario’s name, folder, blueprint, or scheduling.

delete_scenario

Permanently delete a scenario.

clone_scenario

Create a copy of an existing scenario for reuse or modification.

get_blueprint

Fetch the blueprint for a scenario, including module flow and configuration.

update_blueprint

Update the scenario blueprint to modify its module flow.

set_interface

Define input parameters for on-demand scenarios to shape how AI assistants interact with them.

get_logs

Retrieve incomplete execution logs (DLQ) for debugging.

activate_scenario

Activate a scenario to enable scheduled executions.

deactivate_scenario

Deactivate a scenario to pause scheduled executions.