One connection that lets your AI act across thousands of apps.

Breadth is the reason to pick it: one request can chain actions across several apps, such as finding a contact in your CRM and then emailing them.

What it is

Zapier's remote MCP server at mcp.zapier.com. It runs each action through the app connections already in your Zapier account, so your AI never handles another app's password or key. It runs on your existing Zapier plan, with no separate MCP bill.

What you get

Actions found and switched on as a conversation needs them, from apps you have connected
Read actions, such as finding an email or looking up a contact
Write actions, such as sending a message, creating a task or updating a record
Several apps in one request, for example finding a contact in your CRM and then emailing them
Saved Zapier skills listed, created and reused
In early access: whole workflows built, test-run and published to Zapier from the conversation

Requirements

A Zapier account.
In supported clients such as Claude, ChatGPT, Cursor and VS Code you sign in with OAuth, and Zapier sets up the server for you; other clients and your own code use a connection token from mcp.zapier.com.
Your client must support Streamable HTTP, since SSE-only clients cannot connect.
Each successful call uses two tasks from your Zapier plan; failed calls do not count.
Treat a connection token like a password, since anyone holding it can run your tools.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen