← All integrations

Make MCP server

24 operations0 webhooks

Manage and run Make automation scenarios.

Try Make with your agent

Connect Make, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Make on my account, then run one read-only example and show me the result.

Runs once, when you ask

Make tools and triggers

Tools are what your agent can do in Make through Corsair's MCP server. Triggers are the Make events a routine can start from.

Scenarios

  • ActivateDestructive

    Activate scenario

    scenarios.activate

  • Add Build VariablesWrite

    Add new buildtime variables to scenario metadata

    scenarios.addBuildVariables

  • CloneWrite

    Clone scenario

    scenarios.clone

  • Count TrashRead-only

    Count scenarios in trash

    scenarios.countTrash

  • CreateWrite

    Create scenario

    scenarios.create

  • DeactivateWrite

    Deactivate scenario

    scenarios.deactivate

  • DeleteDestructive

    Delete scenario

    scenarios.delete

  • Delete Build VariableDestructive

    Delete buildtime variable

    scenarios.deleteBuildVariable

  • GetRead-only

    Get scenario details

    scenarios.get

  • Get Ai Agent ModulesRead-only

    Get AI agent module details for scenarios

    scenarios.getAiAgentModules

  • Get InterfaceRead-only

    Get scenario interface

    scenarios.getInterface

  • Get Module DataRead-only

    Check module data

    scenarios.getModuleData

Connect Make to Claude, ChatGPT or Cursor

  1. 1

    Connect Make in Corsair

    Add your Make API key once in Corsair. Corsair stores the credential encrypted and makes the Make API calls for your agent, so it never goes into a prompt or a config file. Connect Make

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Make. On a ChatGPT personal plan, connect Make here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Make's read and write operations run right away and its 7 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/make, add the Make plugin, and connect with an API key. Then call methods like corsair.make.api.scenarios.activate() from your app. Corsair keeps each tenant isolated.

Yes. Make requires an API key from your Make account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Make, GitHub, Notion, Stripe, and the rest. Trigger Make from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage and run Make automation scenarios. Common builds include sync jobs, admin tooling, and agents that call Make APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Make API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/make in the open repo. When Make ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Make data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Make data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Make on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 7 destructive Make operations. You can change a link's mode at hub.corsair.dev/me.