The MCP Client integration enables you to connect to remote Model Context Protocol (MCP) servers from within Zapier. Each MCP server has various tools you can use as triggers or actions to build your workflows.

Beta

MCP Client is a beta feature. It’s available for use, but still in active development and may change.

Prerequisites

To connect to a remote MCP server using MCP Client:

• Check you have the necessary authentication credentials as stated in the MCP server documentation.
• Follow the server-specific connection instructions provided by each company. Instructions and requirements will vary.

Note

You should only connect to remote MCP servers you trust. Before connecting, review the server’s security policies and conditions of use.

Connect to MCP Client

To create an app connection to a remote MCP server on Zapier: 

• Go to the Apps page.
• Click + Add connection.
• A new dialog box will appear. Search for and select MCP Client.
• Click Add connection.
• A Connect an Account page will open in a browser tab or window.
• Complete the following fields:
  • Server URL: Enter the server URL.
  • Transport:  Select which transport your client supports:
    • Streamable HTTP
    • SSE
  • OAuth: Select if the remote MCP server requires OAuth connection or not. If you select “Yes” the Bearer Token field will be ignored.
  • (Optional) Bearer Token: Enter the bearer token, if required for authentication.
  • Click Yes, Continue to MCP Client. A new browser tab or window will open.

• Log into your desired remote MCP server to authenticate.
• Grant Zapier permission to access your account if prompted to.

Your remote MCP server is now successfully connected to Zapier. If the account name does not include the server name, you should rename it now. This will help you identify it later if you add more servers. 

Troubleshoot connections to remote MCP servers

App connection does not appear in the Zap editor

After connecting to your remote MCP server, if it does not appear within the Zap editor, you may need to refresh the page.

Immediate reconnection required

If you connect to a remote MCP server but are immediately asked to reconnect, check the following:

• Permissions: Confirm you have the necessary permissions. Some servers require you to be on an allowed client list.
• Server connection requirements: Review your MCP server documentation and make sure the fields completed on the Connect an Account page are correct. For example, the server may only support SSE, and previously you selected Streamable HTTP.

After ensuring the server's settings are correct, reconnect your account.

Available triggers, searches, and actions

Response content types

An MCP tool response includes an array of content types within the result object.

A typical valid MCP tool response looks like this:

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Hello world"
      }
    ]
  }
}
 

The MCP Client integration returns the complete response, because the required data will vary based on the server, tool, and specific use case.

Often, the Text Content will be a JSON string, like:

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"temperature\":30}"
      }
    ],
    "structuredContent: {
      "temperature": 30
    }
  }
}
 

The response also includes the JSON as structured content. Not all MCP servers provide this, but if the Parse Content field is enabled, the integration automatically attempts to parse the first text value as JSON and store it under structuredContent.

Review the MCP documentation to learn about other content types a MCP server tool can use when responding.

Error handling

Unsuccessful MCP tool responses have the following structure:

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Some error message"
      }
    ],
    "isError": true
  }
}
 

If the Handles errors field is enabled, the action will error and display the message extracted from the response. If disabled, the action will always be either Success (Zaps) or Completed (Agents). 

Limitations

• MCP Client only supports tool calls.
• MCP Client only supports connecting to remote MCP servers that use either Streamable HTTP and SSE for their transport methods.