Hitting Zapier MCP’s task limits? Compare what’s on the meter.
Zapier MCP puts an enormous catalog behind one endpoint — and puts every tool call, read or write, on your plan’s task meter at two tasks a call, drawn from the same pool your Zaps use. Gentkey meters a different thing: reads are unmetered on every tier, and writes run through a policy gate — capability-typed grants, dollar and velocity constraints enforced by arithmetic, dry runs, and an audit trail that records denials too. If your agents keep running the account dry, this page is the honest comparison.
Zapier MCP’s pricing, stated plainly.
Per Zapier’s own pricing page and MCP usage docs (as of late August 2026): MCP is included on every Zapier plan, and each successful tool call consumes two tasks from the same task allowance your Zap workflows use — reads and writes alike, tests included; only failed calls are free. When the allowance runs out, MCP tool calls stop working until it resets at the next billing period or you upgrade. The Free plan includes 100 tasks a month — at most 50 successful tool calls, shared with whatever your Zaps consume — and paid plans start at $19.99/month (billed annually) for 750 tasks.
Gentkey meters the opposite thing: reads are unmetered on every tier, and the unit that scales with price is the governed write — a state-changing call that executes upstream under a grant. Denied calls and dry runs never count, and an agent that reads all day costs the same as one that reads once. The reasoning is on the pricing page.
Aggregation both do. Governance is the gap.
Capability-typed write grants
Not “which actions does the server expose” but “which state changes may the agent make”: google-ads.write.budget is a different grant from google-ads.campaigns.mutate, and unclassifiable writes fail closed to the broad grant.
Dollar and velocity bounds
Grants carry hard limits — max $ change per call, max $ moved per hour and day, max writes per hour. The gate does the arithmetic before the upstream service sees the request.
Plan/commit dry runs
Curated writes are split into plan() and commit(). A dry run reports exactly what would change — and skips commit() structurally, not by convention.
Denials are first-class records
Every decision is logged with the agent, tool, and reason — allowed, denied, or denied by constraint. The calls that didn’t happen are the ones you most want on record.
One-flip write freeze
An emergency stop that beats every grant: all writes deny instantly while reads stay up, so you can watch what agents attempt while deciding what to revoke.
Depth first, breadth included
21 curated connectors with typed grants, a 1,798-service directory, and any remote MCP server by URL — upstream tools default to write-gated.
Side by side, without spin.
| Zapier MCP | Gentkey | |
|---|---|---|
| Pricing meter | Two tasks per successful tool call — reads and writes alike — from the account’s shared task pool (Free: 100 tasks/mo, so at most ~50 calls) | Governed writes only — reads, denials, and dry runs are never metered |
| At the limit | MCP tool calls stop working until the allowance resets or you upgrade | Reads never stop — there’s no read meter to run out |
| Catalog | 9,000+ apps, 30,000+ actions, no limit on tools per server | 21 curated connectors with typed grants + 1,798-service directory + any MCP server by URL |
| Write governance | You choose which actions the server exposes to the client | Capability-typed grants per state change; unclassifiable writes fail closed to the broad grant |
| Spend safety | Not a documented feature (as of Aug 2026) | Max $ per call plus hourly/daily dollar and write-velocity windows, enforced before the upstream call |
| Dry runs | Not a documented feature (as of Aug 2026) | plan/commit boundary; curated writes advertise a dry_run argument |
| Denied-call audit | Not a documented feature (as of Aug 2026) | Every decision logged and attributed per agent — allowed, denied, denied by constraint |
| Emergency stop | Not a documented feature (as of Aug 2026) | Write freeze: one flip denies all writes instantly; reads stay up |
The Zapier column reflects zapier.com/mcp, zapier.com/pricing, and Zapier’s MCP usage documentation as checked on August 27, 2026. Their product moves fast — verify against their current pages; “not documented” means we couldn’t find it, not that it can never exist.
Ten minutes, one connection at a time.
Sign in at gentkey.com, connect an account (OAuth or API key — credentials are encrypted at rest and never enter any agent’s context), grant the write capabilities you actually want agents to have, then point each client at your endpoint. Run it alongside your current setup until you’re satisfied.
https://app.gentkey.com/mcpclaude.ai (web & mobile) · Claude Code · Cursor · any MCP clientclaude.ai (web & mobile)
- Settings → Connectors
- Add custom connector
- Paste
https://app.gentkey.com/mcpand finish the OAuth prompt
Claude Code
claude mcp add --transport http \
gentkey https://app.gentkey.com/mcpCursor
// .cursor/mcp.json
{
"mcpServers": {
"gentkey": { "url": "https://app.gentkey.com/mcp" }
}
}Where Zapier fits better.
If you need the breadth of 9,000+ apps behind one server, Zaps and trigger-driven workflow automation outside MCP entirely, or a setup a non-technical teammate finishes without touching a config file, Zapier ships things Gentkey doesn’t — and Gentkey doesn’t automate workflows at all. Gentkey’s curated depth is 21connectors — the app-stack verticals get semantic, dollar-aware constraints, and everything else gets custody, gating, and audit through the directory or a raw MCP URL. If your requirement is “maximum app surface, metered per call,” stay put. If it’s “agents with real account access, inside enforced bounds, without a read meter,” that’s what Gentkey is for.
Fair questions.
What are Zapier MCP's limits, exactly?
Per Zapier's own docs (checked August 27, 2026): each successful MCP tool call consumes two tasks from the same task allowance your Zaps use, failed calls don't count, and when you hit your plan's task limit, MCP tool calls stop working until the allowance resets or you upgrade. Zapier's Free plan includes 100 tasks a month, which works out to at most 50 successful tool calls — reads included, and fewer if Zaps are drawing from the same pool.
Do I have to move everything at once?
No. Gentkey is one more MCP URL — point a client at it alongside Zapier MCP, move connections one at a time, and retire the old endpoint when nothing depends on it. Nothing about the migration is all-or-nothing.
Does Gentkey meter reads?
No. Reads are unmetered on every tier. The metered unit is the governed write — a state-changing call that executes upstream under a grant. Denied calls and dry runs don't count either.
Can Gentkey replace my Zaps?
No, and it doesn't try to. Zaps are trigger-driven workflow automation; Gentkey is an MCP gateway that gives agents governed access to your accounts. If your Zaps work, keep them — moving your agents' MCP traffic to Gentkey just stops that traffic from draining the task pool your Zaps depend on.
Move one connection. Keep the rest.
Connect an account, set a grant with real bounds, and let your agents read for free.