- Home
- Resources
- Integrations
- MCP Client by Zapier
MCP Client by Zapier Zapier integrationAutomate MCP Client by Zapier with Zapier.
The MCP Client by Zapier Zapier integration gives you 2 triggers, 1 action and 1 search. It plugs a remote MCP server into your Zaps: watch its tools, run one, or read from a read-only tool. Below: costs, connection, a first Zap and the traps.
Verified Trustpilot reviews · AI, automation & growth agency
What the MCP Client by Zapier Zapier integration is for
The MCP Client by Zapier Zapier integration connects your automations to any remote MCP server, meaning a server outside Zapier that offers tools Zapier can run for you. Zapier can watch that server for new tools or for new results, run one of its tools as a step, or call a read-only tool to fetch data in the middle of a flow.
Three results you can build with it. An alert when the server gains a tool. New Tool spots a tool that was not there before and a chat message tells whoever maintains your Zaps. A running log of a read-only tool. New Tool Result picks up each fresh result and a spreadsheet row keeps it. A tool run from another app. A form entry or a new row elsewhere starts the Zap, and Run tool sets the server to work.
What Zapier does not do here is just as useful to know. Neither trigger is instant: both are checked on a timer, so nothing reaches Zapier straight away, whatever your plan. New Tool Result and Run Read-Only Tool only see tools the server marks as read-only, and Zapier cannot change that flag; only the server owner can. There is no find-or-create variant either. And Zapier never adds tools to your server: it runs what the server already offers.
Comparing platforms for this kind of flow? Open our n8n vs Zapier comparison.
Zapier words you will meet on this page
Eight terms, one line each, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts a Zap. Here, either a new tool on the MCP server or a new result from one of its read-only tools.
- Action
- What the Zap does once started: the step that writes, sends or runs something for you, such as Run tool on the server.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's count is a count of those.
- Polling vs instant
- Polling: Zapier asks the app for new items on a timer. Instant: the app reports the event itself. Both triggers here are polling.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Search step
- A step that looks up something that already exists, so the following steps can use what it found. Run Read-Only Tool is one.
- MCP server
- The remote server MCP Client by Zapier talks to. It offers tools, and marks some of them as read-only.
What an MCP Client by Zapier Zap really costs
The checks Zapier runs on your server are free. What you pay for is the actions that succeed.
- Triggers2, both polling
- Tasks per successful Run tool1
- Free plan100 tasks a month, two-step Zaps
- Reserved to paid plansNo
Neither trigger ever costs a task, however often Zapier looks. Each successful Run tool counts one task, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited two-step Zaps, and this app is not reserved to paid plans. A filter, a second action or a Run Read-Only Tool search makes the Zap multi-step, which needs a paid plan. Both triggers poll, so the interval grid below applies to each of them.
Connect MCP Client by Zapier in 3 steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. Before that, make sure you have an account on the remote MCP server you want to reach.
- 02
Pick MCP Client by Zapier
Search for MCP Client by Zapier in the dialog, pick it and click Add connection. A tab opens for you to sign in. The connection you save here is reused by every step that talks to that server.
- 03
Sign in and grant access
Sign in in the tab that opens and grant Zapier access to the account. If the tools you plan to run belong to someone else, you need read or write access to them first.
Your first Zap: hear about new tools on your MCP server
GoalPost a chat message whenever the MCP server offers a new tool that passes your filter.
- 01
Build: pick New Tool
Start a new Zap, choose MCP Client by Zapier as the app that starts it and New Tool as the trigger. Select the connection you saved earlier.
- 02
Set Read Only, then test
Use the Read Only option to keep read-only tools or the others, then test. Zapier brings back the three most recent items, so pick a real tool to map from.
- 03
Add the filter
From the plus icon, add a Filter and fill its three boxes: the field to look at, the rule, and the value. Pick a text rule for text and a number rule for numbers, or it never passes.
- 04
Add the chat action
Add your team chat as the action app, choose its send-message event and map the tool details from the trigger into the message.
- 05
Test, then publish
Test the action and read what came back in the chat. If it looks right, click Publish to switch the Zap on. With the filter, this Zap is multi-step and needs a paid plan.
MCP Client by Zapier triggers
2 events start a Zap when something happens in MCP Client by Zapier. Zapier checks for them at the interval your plan allows.
New Tool Result
Polling triggerIn Zapier“Triggers when a read-only tool returns a new result.”
Starts the Zap each time a read-only tool on your MCP server returns a result Zapier has not seen before. You pick the tool once, and every fresh result becomes data the next steps can use.
New Tool
Polling triggerIn Zapier“Triggers when a new tool is available.”
Watches the list of tools your MCP server offers and starts the Zap when one shows up that was not there at the previous check. It reacts to the catalogue, not to what a tool returns.
MCP Client by Zapier action
MCP Client by Zapier gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Run tool
ActionIn Zapier“Run a tool on an MCP server, returning one result.”
Runs one tool on the MCP server and hands its single result to the steps that follow. You choose that tool in the required Tool field.
MCP Client by Zapier search
1 search step looks for data that already exists in MCP Client by Zapier, so a later step can use it.
Searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the result is not the one you expected.
Run Read-Only Tool
SearchIn Zapier“Run a read-only tool on an MCP server, returning one or more results.”
Calls a read-only tool on the server in the middle of a Zap and passes on one or more results, so later steps get data no earlier step carried.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create. MCP Client by Zapier offers no find-or-create variant, so Run Read-Only Tool only reads.
- If multiple search results are found?Three ways out when several items come back: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When an MCP Client by Zapier Zap breaks
Zapier attaches one help article to this app, about connecting remote MCP servers with MCP Client. No limit specific to the app is on record, so the other failures come from how Zapier works in general.
Six cases worth knowing before you publish. If one of them hits a live Zap, see our Zapier troubleshooting guide.
A tool is not in the list
New Tool Result and Run Read-Only Tool only list tools marked as read-only. If one is missing, the server may not flag it; the server owner has to.Errors from the tool itself
Run tool, New Tool Result and Run Read-Only Tool carry a Handle errors option for tool execution errors. Test both settings before relying on one.No backlog
A Zap only reacts to what happens after it is switched on. Tools and results that existed before are not picked up; moving them is a separate job.Loops
As a general precaution, a Zap that writes into the place its own trigger watches can set itself off again and again and burn through tasks.Big batches held back
If the server suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.Seen once, used once
On a polling trigger Zapier keeps track of what it has already seen, so the same tool or result does not start the Zap twice.
Need help automating MCP Client by Zapier with Zapier?
A person reads every message.



