> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/mcp-server/connect-using-api-key/usage-with-vapi.md).

# Usage with Vapi

This guide outlines how to connect Make MCP server to Vapi.

### Prerequisites

* [Vapi](https://dashboard.vapi.ai/register) account
* [API key](https://developers.make.com/mcp-server/connect-using-api-key.md)

### Connect to Vapi

To connect Make MCP server to Vapi:

1. Open your Vapi account.
2. Navigate to **Tools** on the left sidebar.
3. Click the **Create Tool** button, then select **MCP**.
4. Configure the tool name and describe when to use the tool.
5. In **Server URL**, add the following URL:

```
https://<MAKE_ZONE>/mcp/u/<API_KEY>/v2
```

6. Replace `<MAKE_ZONE>` and `<API_KEY>` with your actual values.

* `MAKE_ZONE` : The zone your organization is hosted in. For example, `eu2.make.com`.
* `API_KEY`: Your API key for MCP.

7. In **Timeout**, enter an appropriate timeout for your use case.
8. In **MCP Settings**, select **Streamable HTTP**.
9. Click **Save**.

You've now connected Make MCP server to Vapi.

{% hint style="warning" %}
MCP tool calls from Vapi Assistants may exceed Make API rate limits and result in errors. To check the Make API rate limit defined in your plan, see [Make API rate limits](https://developers.make.com/api-documentation/getting-started/rate-limiting).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.make.com/mcp-server/connect-using-api-key/usage-with-vapi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
