Skip to main content
    My stack

    Plug Make into your assistant

    If you already have Make scenarios running, plug it in: your assistant runs them in one sentence, on every plan. With no scenario ready, it has nothing to run, and letting it edit them takes a paid plan.

    In Make, your assistant can read and edit your data. Plans: running your scenarios works on every Make plan. Connecting takes one click from Claude.

    Official, published by Make · checked on 16 November 2026

    What changes for you

    Everyday situations, and what to write to your assistant.

    1. Client invoice

      The scenario runs, Make stays closed.

      Run my “Client invoice” scenario for Studio Martin, website redesign, and tell me what it returns.

    2. Your automations

      The manual for your workshop.

      Which Make scenarios can you run for me, and what does each one do?

    3. Monthly report

      The result, even when it takes a while.

      What's the status of the monthly report scenario you started earlier? Give me its result.

    From one freelancer to another

    Make is the workshop where you tinkered with your automations one Sunday, and which you'd rather not reopen. The MCP server turns it into a remote control: your assistant presses the button for you and hands over the right details. But it only presses the buttons you've prepared, and it understands them only as well as you've described them. Here's how to make its job easy.

    What works

    • Describe your scenarios

      Make says so: a detailed description helps the assistant pick the right scenario. “Scenario 7 copy” tells it nothing, and tells you nothing either.

      Source: developers.make.com
    • Well-named inputs

      Scenario inputs are what the assistant fills in when it runs it. Name them clearly (client, amount, email) and it'll know what goes where.

      Source: developers.make.com
    • Active and “on demand”

      A scenario only shows up if it's active and scheduled “on demand”. If one is missing, check those two settings first.

      Source: help.make.com
    • Run first, manage later

      When connecting, only tick the run permissions if you don't want it touching your scenarios. Management can be added the day you need it.

      Source: help.make.com
    • A made-to-measure toolbox

      To expose only a few scenarios, use an MCP toolbox: you pick which ones, and mark as read-only those that change nothing.

      Source: help.make.com

    Where it falls short

    • Long scenario, lost answer

      After a short wait, the assistant stops waiting for the answer, even though the scenario keeps running in Make. Workaround: grant scenario read access when connecting, then ask it for the result a little later.

      Source: developers.make.com
    • Connected, but nothing runs

      ChatGPT users report a working connection, but scenarios that never run. Workaround: check the scenario is active and “on demand”, give it a description, then look at its history in Make.

      From user reports · community.make.com
    • Hand-edited config gets stuck

      A Claude Desktop user who had added Make by hand to the config file kept hitting an authorisation error. Workaround: remove Make from the config file and add it as a connector from Claude, signing in with your account.

      From user reports · community.make.com
    • On free, it only runs

      On the free plan, it runs your scenarios but can neither inspect nor edit them. Workaround: make your edits in Make, or move to a paid plan if you plan to hand it the workshop.

      Source: help.make.com

    Plug in Make

    Pick your assistant: the steps follow.

    1. Open Make's page in Claude's directory and add the connector.

      Open in Claude
    2. Connect your Make account and read the access requested.

    3. Check it by asking:

      Run my invoicing scenario for this client.

    Depending on your plan. Plus, on paid plans: managing your scenarios, connections and data stores.

    Stay in control

    The assistant never has more rights than your account.

    What it can do

    Make does not name its tools: they are generated from your scenarios and granted permissions.

    ActionIdentifier
    Edits your data2
    Run your active, on-demand scenarios (all plans)
    View and edit scenarios, connections, data stores (paid plans)
    Read onlyNo effect on your data
    View scenarios, teams, connections, webhooks and data stores (paid plans).

    Actions as the vendor documents them.

    Your safeguards

    You choose the permissions

    When connecting, you choose the permissions: run your scenarios, or manage them too.

    A single organisation

    With account sign-in, you can limit access to a single Make organisation.

    Only your ready scenarios

    Only your active, on-demand scenarios become actions.

    Our view

    Useful if

    You already have Make scenarios and want to run them in one sentence.

    Less useful if

    You have no automation yet: the server is mostly for running and managing existing scenarios.

    Going further

    Compare the 19 official MCP servers

    The guide to get started