# Make MCP events

Hookdeck Event Gateway turns the webhooks it receives from Make into MCP events for agents.

These pages cover requests a Make scenario sends to your endpoint. To send data into Make and trigger a scenario, see Make's [Webhooks docs](https://help.make.com/webhooks) and [how to solve Make webhook rate limit errors](/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors).

Agent skill: `npx skills add hookdeck/webhook-skills --skill make-webhooks` ([details](https://hookdeck.com/webhooks/make/skill))

> Independent reference generated from hookdeck/webhook-registry (commit ff7f882, 20 Nov 2026). [Make's official docs](https://apps.make.com/api-key-authentication-type).

[Overview](https://hookdeck.com/webhooks/make) · [MCP events](https://hookdeck.com/webhooks/make/mcp-events) · [Verify signatures](https://hookdeck.com/webhooks/make/verify) · [Production guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts) · [Agent skill](https://hookdeck.com/webhooks/make/skill)

## Make's MCP server

Make's MCP server lets MCP clients such as Claude and ChatGPT run scenarios and manage your Make account. Those tools call Make; they don't deliver the requests your scenarios send. To get those requests into an agent, point the module at Hookdeck Event Gateway, as described below. [Make's MCP docs](https://developers.make.com/mcp-server)

## How to subscribe

1. Connect your agent to Hookdeck's MCP server ([MCP Events bridge](https://hookdeck.com/blog/mcp-events-bridge)).
2. Point your Make webhook at a Hookdeck source.
3. Your agent lists the available events and subscribes to the ones it needs.
---

Not affiliated with Make. Facts are compiled from public sources and linked inline. [View as JSON](https://hookdeck.com/webhooks/make.json) · [Report a correction](https://hookdeck.com/contact)
