> 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.

# MCP providers

> Connect a Vapi MCP tool to Zapier, Composio, or Make MCP servers, with the server URL, auth header, and links to each provider's setup documentation.

This page shows the server URL and authentication for common MCP providers, with links to each provider's own setup steps. To create the MCP tool itself, see [MCP tools](/tools/mcp).

Each provider controls which tools its server exposes. Vapi adds every tool the server lists, so limit the tools at the provider. For more information, see [Choose which tools the voice agent gets](/tools/mcp/configure#choose-which-tools-the-voice-agent-gets).

## Zapier

Zapier's MCP server supports Streamable HTTP only. Vapi connects with a connection token.

#### Create the server

Create a server at [Zapier MCP](https://mcp.zapier.com) and add the apps and actions the voice agent can use. See [How Zapier MCP servers work](https://docs.zapier.com/mcp/overview/how-servers-work).

#### Generate a connection token

Generate a connection token for the server. Zapier shows the token only once, and generating a new one stops the old one from working. See [How connections work](https://docs.zapier.com/mcp/overview/how-connections-work).

#### Connect the MCP tool

On the MCP tool, set the server URL to `https://mcp.zapier.com/api/v1/connect` and add this header:

```text
Authorization: Bearer YOUR_ZAPIER_CONNECTION_TOKEN
```

For more information, see Zapier's [Connect any other MCP client](https://docs.zapier.com/mcp/get-started/connect/other).

## Composio

#### Create the server

Create an MCP server for the toolkit you need and generate its URL. See [Single toolkit MCP](https://docs.composio.dev/docs/single-toolkit-mcp).

#### Connect the MCP tool

On the MCP tool, set the server URL to the generated URL and add this header:

```text
x-api-key: YOUR_COMPOSIO_API_KEY
```

Use the URL Composio generates. Don't build it yourself.

## Make

Make's MCP server can expose your active, on-demand scenarios as tools. It can also expose tools that manage your Make account, depending on the API key's scopes.

> **Warning**
>
> Scenario access control applies to scenario tools, not management tools. A broadly scoped API key can expose management tools that can change Make resources. Grant no management scopes unless the voice agent needs them.

#### Prepare the scenarios

Define the inputs and outputs for each scenario, then set its schedule to **On demand**.

#### Create an API key

In Make, open **Profile** > **API access**, click **+ API token**, and create an API key with the `mcp:use` scope and only the other scopes the voice agent needs. See [Connect using API key](https://developers.make.com/mcp-server/connect-using-api-key).

#### Connect the MCP tool

Set the server URL to `https://<MAKE_ZONE>/mcp/v2`, where `<MAKE_ZONE>` is your organization's zone, such as `eu2.make.com`. Add this header:

```text
Authorization: Bearer YOUR_MAKE_API_KEY
```

#### Limit scenario access (optional)

By default, the key can use every active, on-demand scenario in your Make organizations. To limit it to an organization, team, or specific scenarios, use the connection URL from Make's [scenarios as tools access control](https://developers.make.com/mcp-server/connect-using-api-key/scenarios-as-tools-access-control). That URL includes the API key, so treat it as a secret.

#### [Run the Make MCP example](https://github.com/VapiAI/vapi-labs/blob/main/projects/vapi-make-patterns/examples/mcp/README.md)

Provision a demo scenario, inspect the tools Make exposes, and verify the round trip between Vapi and Make.

For more information about choosing between MCP, API Request, and Function tools for Make, see [Connect Vapi to Make](/tools/integrations/make).