> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.vapi.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.vapi.ai/_mcp/server.

# Choose a Make integration pattern

> Choose a Make integration pattern for an assistant: API Request for webhooks, Model Context Protocol (MCP) for discovered tools, or Function for call context.

Connect a Vapi assistant to Make to invoke scenarios that coordinate actions and data across apps configured in Make. Use this guide to choose among Vapi's general-purpose API Request, Model Context Protocol (MCP), and Function tools. Start with an **API Request tool** unless the scenario needs dynamic tool discovery or Vapi's `tool-calls` webhook protocol.

## Choose a pattern

| What the Make scenario needs                                                      | Use                                        | Why                                                                                                                            |
| --------------------------------------------------------------------------------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| An ordinary webhook that accepts and returns JSON                                 | **[API Request tool](/tools/api-request)** | Vapi sends the configured HTTP request directly and gives the JSON response to the assistant. This is the recommended default. |
| A curated tool surface that Make owns and Vapi discovers at runtime               | **[MCP tool](/tools/mcp)**                 | Make exposes eligible scenarios as MCP tools and Vapi imports the tools exposed by that server.                                |
| Vapi's `tool-calls` envelope or call, assistant, and artifact context             | **[Function tool](/tools/custom-tools)**   | Vapi sends its webhook payload to the scenario, which must return the expected Function tool response.                         |
| Asynchronous execution or server-driven [Live Call Control](/calls/call-features) | **[Function tool](/tools/custom-tools)**   | Function tools support asynchronous execution, and their webhook payload includes the call context needed for live control.    |

## API Request

Use an API Request tool when Make exposes a webhook that accepts a JSON request and returns a JSON response. If the assistant needs the scenario's result, the Make webhook must return JSON in the request-response flow. Make does not need to parse or construct a Vapi-specific webhook envelope.

This pattern has the smallest integration contract and is the best starting point for most Make scenarios.

## MCP

Use Make MCP when Make should define the tool surface. Make exposes active, on-demand scenarios as tools. Vapi imports every tool exposed by the configured MCP server; Vapi does not apply a separate per-tool filter.

Configure the Make MCP token with least-privilege scopes. Use Make's [scenarios as tools access control](https://developers.make.com/mcp-server/connect-using-mcp-token/scenarios-as-tools-access-control) to expose only the scenarios the assistant needs. See [Make MCP Server](https://developers.make.com/mcp-server) for Make's current connection documentation.

## Function

Use a Function tool when the Make scenario must receive Vapi's `tool-calls` message, including call, assistant, or artifact context. This is also the appropriate pattern for asynchronous execution or live-call actions.

The scenario must parse Vapi's webhook payload and return the [Function tool response](/tools/custom-tools#server-response-format-providing-results-and-context) for synchronous calls. This extra protocol work is unnecessary for an ordinary JSON webhook, so prefer an API Request tool in that case.

## Runnable examples

#### [Vapi + Make patterns](https://github.com/VapiAI/vapi-labs/tree/main/projects/vapi-make-patterns)

Run the API Request and MCP examples and inspect the complete Vapi → Make → Vapi round trip.