Make for AI agents

Make is a visual automation platform that connects apps and services into workflows called scenarios, without requiring a team to write code. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Developer toolsAPI keyMCP + RESTmake.com
AUDIT LOG · MAKEPOLICY: acme-support
09:41:07 · claude · u_8f2read
make.list_teams
List Teams✓ allowed · 212ms
09:41:08 · claude · u_8f2read
make.get_hook
Get Hook✓ allowed · 164ms
09:41:09 · claude · u_8f2write
make.create_organizations
Create Organization✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
make.delete_scenario
Delete Scenario✕ blocked · policy: deny
EVERY MAKE CALL, ON THE RECORD
01 · USE CASES

What agents do in Make.

01

Check a scenario's run logs

Pull recent execution logs for a scenario to debug why a run failed, read-only.

02

Look up a connection's status

Check whether a connection used by a scenario is still active before troubleshooting.

03

Approve before deleting a scenario

Require approval before deleting a scenario, since it stops every automation built on it.

02 · ACTIONS

39 Make actions, graded by risk.

Every Make action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

35

Look things up. Allowed by default.

  • make.get_hook
    Get Hook
  • make.get_team
    Get Team
  • make.list_teams
    List Teams
  • make.get_hook_log
    Get Hook Log
  • make.get_users_me
    Get Current User
  • make.get_connection
    Get Connection
  • make.get_operations
    Get Operations
  • make.list_scenarios
    List Scenarios
  • make.get_organization
    Get Organization
  • make.list_connections
    List Connections
  • make.get_scenario_logs
    Get Scenario Logs
  • make.get_cashier_prices
    Get Cashier Prices
  • make.list_enums_locales
    List Enums Locales
  • make.list_organizations
    List Organizations
  • make.get_enums_imt_zones
    Get Enums IMT Zones
  • make.get_cashier_products
    Get Cashier Products
+ 19 MORE

write

2

Create and change things. Allow, or ask the user first.

  • make.update_scenario
    Update Scenario
  • make.create_organizations
    Create Organization

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • make.delete_scenario
    Delete Scenario
  • make.create_users_password_reset_demand
    Create Password Reset Demand
03 · HOW IT WORKS

Make in three steps.

  1. 01Your users connect MakeThey add their Make api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Organization” can wait for the user, and “delete Scenario” can be denied outright.
  3. 03Any agent can actYour agent calls Make through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('make', {
  read: 'allow',
  write: 'ask',        // create_organizations
  destructive: 'deny',  // delete_scenario
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Make connects.

Users add their Make api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Make connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Make from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Make and Arc0, answered.

Q01

Can I use Make with Claude, ChatGPT or Cursor?

Yes. Connect Make to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Make actions you allow.

Q02

How do users connect Make?

Users add their Make api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Make actions can my agent take?

39 in total: 35 read, 2 write and 2 destructive, such as “create Organization”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Make?

Yes. Actions like “delete Scenario” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Make too?

Yes. The same Make connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Make into your agent.

Your users connect Make once, under your brand. Your agent gets 39 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan