---
ref: tool:make/create-scenario
name: Create a scenario
company: company:make
workflows: []
access: [mcp, cli, api]
tags: [capability:automate-workflows, category:automation, has:api, has:cli, has:mcp]
docs: https://developers.make.com/api-documentation/api-reference/scenarios
updated: 2026-09-27
---

# Create a scenario

Creates a Make scenario in a team from a blueprint of modules and a schedule, and returns the new scenario's details.

`teamId`, `scheduling` and `blueprint` are required; the blueprint lists the
modules, their parameters and the connections they use. A new scenario is
inactive: activate it with `scenarios_activate`, `make-cli scenarios activate`
or `POST /scenarios/{scenarioId}/start` before running it.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "make": { "url": "https://mcp.make.com" } } }
```

Call the MCP tool `scenarios_create`.

Server URL: https://mcp.make.com

### CLI (official)

Install the command, then confirm it runs.

```sh
npm install -g @makehq/cli
make-cli --version
```

Run `make-cli scenarios create`.

Set `$MAKE_API_KEY` in your environment first.

### API (official)

- Base URL: https://{zone_url}/api/v2
- Endpoint: `POST /scenarios`
- Auth: send the header `Authorization: Token $MAKE_API_KEY`
- Docs: https://developers.make.com/api-documentation

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.