← MCP

Zapier MCPZapier MCP

Zapier

MCPMCP 多应用Multiple applications 聚合入口Aggregated access 远程托管Remote-hosted action白名单Action allowlist partial lifecycle: active 核验Checked 2026-10-30

English summaries and interface labels are available. Detailed source notes below are currently in Chinese.

Zapier MCP 是「千余应用的入口」：你在 Zapier 侧勾选哪些 action，agent 就有哪些工具—— 工具面是白名单生成的，不是厂商预置全量。这个结构本身就是收紧手段：没勾的不存在。

Zapier MCP is an entry point to a thousand apps: whatever actions you tick in Zapier's config become the agent's tools — the tool surface is allowlist-generated, not vendor-preset. That structure is itself a tightening measure: unticked means nonexistent.

适合与不适合When to use it, when not to

适合：agent 要跨多应用干活、要按 action 粒度控权限。不适合：要单应用最深工具面（用官方单厂商 server）；免费假设。

Fits: agents working across many apps, permission control at action granularity. Not a fit: needing the deepest single-app tool surface (use that vendor's own server); free assumptions.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Zapier, Inc.（美国）。Zapier, Inc. (US).
国内使用Direct access: 大陆可直连direct OK　actions.zapier.com 直连实测 200（2026-10-21）。actions.zapier.com measured 200 direct (2026-10-21).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它是「千余应用的入口」：用户在 Zapier 侧挑选哪些 action 暴露给 agent，server 把这些 action 包装成 MCP 工具。
It calls no model itself — an interface implementation called by MCP clients. It is "an entry point to a thousand-plus apps": the user picks on the Zapier side which actions are exposed to the agent, and the server wraps those actions as MCP tools.
运行位置Where it runs: 官方托管远程 server（actions.zapier.com 文档线直抓 200）；每用户按配置生成专属端点。
Official hosted remote server (actions.zapier.com docs line direct fetch 200); each user gets a dedicated endpoint URL generated from their configuration.
本地文件Local files: 不碰本机文件系统——它代执行的是 Zapier 平台侧的 action（读写各 SaaS 应用）。
Never touches the local file system — what it executes on your behalf are Zapier-platform-side actions (reading and writing various SaaS apps).
关机后的任务Tasks after shutdown: 服务在 Zapier 侧；请求-响应语义。注意：Zapier 平台的 Zap（自动化线）是常驻自动化—— 那是 automation 大类的另一产品面，不算 MCP server 本体。
The service lives on Zapier's side; request-response semantics. Note: Zapier's platform Zaps (the automation line) are resident automations — that is another product surface in the automation category, not part of this MCP server itself.
工具与扩展Tools & extensions: 动态工具面：暴露哪些工具=用户在 Zapier MCP 配置里勾选了哪些应用的哪些 action （Gmail/Sheets/Notion/Slack…千余应用）。工具清单因人而异，无法逐条清点——这是它与其他厂商 server 最大的结构差异。
A dynamic tool surface: which tools are exposed = which actions of which apps the user checked in the Zapier MCP configuration (Gmail/Sheets/Notion/Slack… a thousand-plus apps). The tool inventory varies per person and cannot be enumerated item by item — this is its biggest structural difference from other vendor servers.
上下文与记忆Context & memory: 无 server 侧跨会话记忆——状态在各目标应用里。
No server-side cross-session memory — state lives in the various target apps.
权限与限制Permissions & limits: 两层权限叠加：Zapier 侧「勾选哪些 action」是第一层白名单；各目标应用的 OAuth 授权是第二层。写能力跟着勾选走——没勾的 action 不存在，这是它相对「单应用全权限 server」的结构性收紧优势。
Two permission layers stack: the Zapier-side "which actions are checked" is the first allowlist layer; each target app's OAuth authorization is the second layer. Write capabilities follow the checkboxes — unchecked actions do not exist, which is its structural tightening advantage over "single-app full-permission servers".
适合什么任务Best for: 适合：一个 server 接多应用（agent 要同时碰 Gmail+Sheets+CRM 时）、按 action 白名单收紧。不适合：要单应用深度工具面（官方单厂商 server 更深）；要免费（Zapier 套餐线约束）。
Fits: one server reaching many apps (when an agent needs to touch Gmail+Sheets+CRM at once), tightening by action allowlist. Not a fit: needing a deep single-app tool surface (official single-vendor servers go deeper); expecting free (Zapier plan-line constraints).
传输方式Transport: Streamable HTTP 远程托管（每用户专属端点 URL）；核验：actions.zapier.com 文档 200（2026-10-21）。
Streamable HTTP remote hosting (a dedicated endpoint URL per user); verified: actions.zapier.com docs 200 (2026-10-21).
认证机制Authentication: 端点 URL 本身带鉴权语义（专属密钥端点）+ 各目标应用 OAuth；端点泄露=权限泄露——保管口径按凭据级。
The endpoint URL itself carries authentication semantics (a dedicated secret endpoint) + OAuth for each target app; endpoint leak = permission leak — treat its custody at credential grade.
权限范围Permission scope: 作用域=勾选的 action 集合；读写都有（跟着 action 性质）。白名单是第一层收紧；无逐操作审批机制的官方说明。
Scope = the checked action set; both read and write (following each action's nature). The allowlist is the first tightening layer; no official docs for a per-operation approval mechanism.

头号误解Top misconception

把「千余应用」当「千余工具都开着」——工具面=你勾选的 action 白名单Reading 'a thousand apps' as 'a thousand tools are enabled' — the tool surface is the action allowlist you ticked
与 Zapier 平台的 Zap 自动化混谈——MCP server 是会话内代执行，Zap 是常驻自动化（automation 大类）Confusing it with Zapier's Zap automations — the MCP server executes within a session; Zaps are standing automations (the automation category)
工具因人而异——对照测试别人配置时别假设工具集相同Comparing against someone else's setup — tool surfaces are per-user; never assume identical tool sets

未知项清单Known unknowns

套餐对 MCP 的约束细则（未逐条核验；D9 不采价格数字）
专属端点的轮换/吊销机制（未逐条核验）
支持应用×action 的完整矩阵（千余应用，未逐条清点）

Plan constraints on MCP details (not verified item by item; D9 does not collect price numbers)
Rotation/revocation mechanism of the dedicated endpoint (not verified item by item)
The complete app×action support matrix (a thousand-plus apps, not enumerated item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
docs	Zapier · 官方 MCP 文档（配置与端点口径，2026-10-21 直抓核验）Zapier · official MCP docs (configuration and endpoint wording, direct-fetched and verified 2026-10-21)	https://actions.zapier.com/docs/platform/mcp/
changelog	Zapier · 官方更新日志（changelog）Zapier · official update log (changelog)	https://zapier.com/blog/updates/
docs	Zapier · 官方 MCP 产品页Zapier · official MCP product page	https://zapier.com/mcp

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.