How to integrate Make MCP with Grok Build

Connect Grok Build to Make MCP. Get all available make operations, show supported languages for make automations, and more from your terminal, with authentication handled for you.

Make logoMake
Api Key

Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code.

53 Tools

How to integrate Make MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Make account to Grok Build through Composio, so it can get all available Make operations, show supported languages for Make automations, list all timezones used in Make, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Make with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Make integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,500+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Make account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Make to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Make account through Composio. On the first Make action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Make

  • Get all available Make operations
  • Show supported languages for Make automations
  • List all timezones used in Make
  • Display language codes for workflow setup

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Make scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

Every Make action and event your agent gets out of the box.

Activate Scenario

Activate a Make scenario; a regularly scheduled scenario may run immediately, executing its configured automation and external effects.

Create Hook

Create a hook without exposing its bearer-like URL, UDID, or relay data.

Create Organization

Tool to create a new organization in Make.

Create Scenario

Create a Make scenario from JSON-encoded blueprint and scheduling data.

Create Password Reset Demand

Tool to create a password reset demand for a user by their email address.

Deactivate Scenario

Deactivate a Make scenario and stop it if it is currently running.

Delete Scenario

Move a Make scenario to trash, where it can be restored for 30 days.

Get Cashier Prices

Tool to retrieve a specific cashier price by its identifier.

Get Cashier Products

Tool to retrieve available cashier products from Make.

Get Connection

Retrieve one Make connection by ID.

Get Current Authorization

Tool to retrieve current authorization details for the authenticated user.

Get Enums Apps Review Statuses

Tool to retrieve available app review statuses in Make.

Get Enums IMT Regions

Tool to retrieve the list of Make regions and their regionId values.

Get Enums IMT Zones

Tool to retrieve available IMT zones in Make.

Get Enums LLM Models

Tool to retrieve available Large Language Models from Make.

Get Enums Module Types

Tool to retrieve available module types in Make.

Get Enums Organization Features

Tool to retrieve available organization features in Make.

Get Enums User API Token Scopes

Tool to retrieve all available API token scopes in Make.

Get Enums User Email Notifications

Tool to retrieve available email notification types for Make users.

Get Enums User Features

Retrieve the list of all existing user features and their descriptions.

Get Enums Variable Types

Tool to retrieve available variable types in Make.

Get Hook

Retrieve a hook without exposing its bearer-like URL, UDID, or relay data.

Get Hook Incoming Activity

Get hook queue statistics or safe metadata for one incoming event; payload values are not returned.

Get Hook Log

Retrieve safe status and timing diagnostics for one Make webhook execution log.

Get Operations

Retrieve daily operations usage for an organization over the past 30 days.

Get Organization

Retrieve detailed information about one Make organization by ID.

Get Public Template Blueprint

Retrieve the complete blueprint for a public approved Make template.

Get Scenario

Retrieve one Make scenario by ID with optional selected columns.

Get Scenario Blueprint

Retrieve a sanitized current, draft, or historical scenario blueprint; credential-bearing URL, auth, header, query, password, secret, and token fields are omitted.

Get Scenario Execution

Retrieve the status, outputs, pause metadata, or error for one execution.

Get Scenario Interface

Retrieve a Make scenario's declared input and output interface.

Get Scenario Logs

List scenario logs, list one module's operation logs, or retrieve one execution log according to the identifiers supplied.

Get Scenario Trigger

Retrieve safe trigger details without exposing its URL or UDID.

Get Team

Retrieve detailed information about a specific team by its ID.

Get Current User

Tool to retrieve information about the current authenticated user.

List Connections

List the connections belonging to a Make team.

List Enums Countries

Retrieve all supported countries in Make.

List Enums Languages

Tool to retrieve a list of language codes and names.

List Enums LLM Builtin Tiers

Retrieve all predefined LLM tiers (small, medium, large) with their associated models, providers, and pricing coefficients.

List Enums Locales

Retrieve all supported locales in Make.

List Enums Timezones

Retrieve all supported timezones in Make.

List Hook Logs

List safe summary metadata for a Make webhook's retained execution logs.

List Incomplete Executions

List failed or unfinished executions for a Make scenario.

List Organizations

Tool to list organizations the authenticated user belongs to (including organizationId, name, and timezoneId).

List Public Templates

Browse public approved Make templates with filters and offset pagination.

List Scenarios

List scenarios belonging to a Make team with offset pagination.

List Teams

Tool to list all teams within an organization.

Ping API

Tool to ping the Make API to verify connectivity and service availability.

Run Scenario

Run an already active Make scenario, executing its configured automation and external effects.

Set SDK Connection API

Replace the complete API definition for a Make SDK app connection.

Update Scenario

Partially update a Make scenario, leaving omitted properties unchanged; optionally authorize installation of an app newly used by the organization.

Update Scenario Interface

Replace an on-demand scenario's input specification; requires Make Pro+.

Verify Connection

Test whether a Make connection's saved credentials can reach its provider.

FAQ

Frequently asked questions

A standalone Make MCP server gives Grok Build a fixed set of Make tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Make and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Make data and credentials are handled to that standard.

Start with Make.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Make tool your agent needs.Free to start.

Start building