Make Launches CLI to Let Developers and AI Agents Manage Automations From the Terminal.

Make has released a command-line interface that brings its automation platform directly into developers' terminals and AI coding environments. The Make CLI, announced this week, lets users create and manage scenarios, connections, data stores, and webhooks without opening the visual builder.

The move addresses a workflow gap for technical teams who want automation power but prefer working in code editors, CI/CD pipelines, and terminal environments. It also positions Make as a backend for AI coding agents like Claude Code and Cursor, which can now control automations through command-line instructions.

The CLI integrates Make into standard development toolchains. Developers can version-control scenarios alongside application code, trigger automation deployments from GitHub Actions or similar tools, and script bulk operations across multiple workspaces.

Make positions this as particularly useful for teams managing dozens or hundreds of scenarios across environments. Instead of manually clicking through the web interface to replicate changes, developers can script updates and execute them in batch. The CLI supports creating and modifying scenarios, managing connections to third-party services, configuring webhooks, and accessing data stores.

The interface is open source, meaning teams can inspect the code, contribute improvements, or fork it for internal modifications. Make has published the CLI documentation on its developer portal, where it joins the company's existing SDK and Model Context Protocol server.

Make now offers five distinct interfaces to its automation engine, each targeting different user types and workflows. The visual platform remains the primary entry point for no-code users. The Make MCP server and MCP Toolboxes let AI assistants like ChatGPT or Claude trigger automations through structured tool calling. The Make SDK enables programmatic control for developers embedding automations inside custom applications.

The new CLI fills the gap for terminal-based work. While the SDK is designed for embedding Make into other software, the CLI is built for developers who live in the command line and want quick, scriptable access without writing SDK code.

This follows Make's broader push into AI-assisted automation. The company recently added support for Claude Opus 4.7 and launched AI Agents with transparency into decision-making processes. The CLI extends that strategy by letting AI coding agents interact with Make through natural terminal commands rather than API calls.

Make warns that the CLI can create, modify, and delete production resources, recommending users test commands in non-production environments first. The tool is available now to all Make users at no additional cost beyond standard operation limits.

For teams using tools like n8n or Zapier, the CLI represents a differentiation point. While those platforms focus primarily on visual or SDK-based access, Make is betting that offering terminal, MCP, SDK, and visual interfaces simultaneously will appeal to organizations with mixed technical teams. The CLI documentation includes installation instructions and sample commands for common workflows.