# Vendor facets — Zapier (Zapier MCP). One hosted MCP server per user at mcp.zapier.com exposing
# 40,000+ actions from 9,000+ Zapier app integrations. The provider's part is the Zapier integration
# it may have built on the Developer Platform; the MCP server itself is Zapier's, per user, on
# Zapier's domain — nothing without a declaration, `platform` (0.25) at most.
vendor: zapier
name: Zapier
website: https://zapier.com
areas:
- mcp-hosting
registry_keys: []
rubric_schema_version: 0.22.0
generated: '2026-09-25'
features_refreshed: '2026-09-25'
basis: capability
summary: >-
  Zapier MCP gives agents every Zapier action through one server per user at mcp.zapier.com; it is a distribution
  channel for an API that has a Zapier integration, not a server the provider owns. The best a provider
  can reach is `platform` (0.25 of 12 agent-readiness points) on mcp_server, and only by declaring it
  — and because the server is per-user, not per-provider, even that is a weak fit. Zapier MCP Skills are
  the end user's Markdown on their own server and earn a provider nothing.
features:
- id: zapier-mcp
  name: Zapier MCP hosted server
  description: >-
    A hosted Streamable HTTP MCP server at mcp.zapier.com, one per MCP client, exposing actions from 9,000+
    apps with Zapier-managed credentials.
  source: https://zapier.com/mcp
  tier: all
- id: tools-from-integrations
  name: Tools derived from Zapier integrations
  description: Each tool is a single action from a Zapier app integration, found through dynamic tool
    discovery.
  source: https://docs.zapier.com/mcp/home
  tier: all
- id: mcp-skills
  name: Zapier MCP skills
  description: >-
    User-created Markdown skills tied to one Zapier MCP server (agentic mode), plus packaged skills built
    by Zapier.
  source: https://docs.zapier.com/mcp/manage/skills.md
  tier: all
- id: developer-platform
  name: Integration Builder (Developer Platform)
  description: >-
    App developers build and publish their Zapier integration with the Platform UI or zapier-platform-cli;
    published actions become available to Zapier MCP.
  source: https://docs.zapier.com/llms.txt
  tier: all
maps:
- feature: zapier-mcp
  check: mcp_server
  layer: agent_readiness
  grade: platform
  credit: 0.25
  conditional: true
  condition: >-
    Only if the provider declares mcp.zapier.com in its own mcp/ manifest. Zapier exposing the provider's
    actions without that declaration earns the provider nothing, and the server is per-user rather than
    per-provider.
  provider_must: Declare the Zapier MCP endpoint; building the Zapier integration itself is not read by
    any check.
  note: A per-user server with one shared tool shape on Zapier's domain is `platform` in 0.22.0.
  points: 12
  baseline_pass_rate: 0.22
earns_nothing:
- feature: mcp-skills
  check: agent_skills
  why: >-
    Skills are written by the Zapier user and live on that user's server; they are not provider-authored
    skills for the provider's API.
- feature: developer-platform
  check: agent_skill_present
  why: >-
    A Zapier integration definition is Zapier's app format; no check reads it as an Agent Skill, SDK or
    contract.
- feature: zapier-mcp
  check: protected_resource_metadata
  why: OAuth happens between the MCP client and Zapier; the provider's host serves nothing new.
- feature: zapier-mcp
  check: dynamic_client_registration
  why: No registration_endpoint is added to the provider's discovery document.
- feature: zapier-mcp
  check: mcp_endpoint_discoverable
  since: 0.23.0
  why: >-
    Each Zapier MCP server is created per user and per client inside a Zapier account; there is no public,
    provider-specific endpoint an agent can construct.
- feature: tools-from-integrations
  check: well_known_catalog
  why: >-
    Listing in Zapier's 9,000-app catalog is Zapier's discoverability, not a WellKnown/APICatalog pointer.
out_of_reach:
  checks:
  - contract_present
  - spec_presence
  - llms_txt_published
  - agent_card
  - auth_clarity
  - delegated_identity
  note: Zapier consumes the provider's API; nothing it ships lands on the provider's own surface.
unscored_practice:
- feature: developer-platform
  why: A provider-built, published Zapier integration is real integration work no 0.22.0 check reads.
surface:
  agent_readiness:
    reachable: 3.0
    total: 139
hard_rule: >-
  A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes
  the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership
  can.
method: searched
source:
- https://docs.zapier.com/llms.txt
- https://docs.zapier.com/mcp/home
- https://docs.zapier.com/mcp/manage/skills.md
- https://zapier.com/mcp
measured:
  cohort:
    method: vendors-catalog.json detections (CNAME / header / URL shape / markup), never a name match
    detected: 0
    in_baseline: 0
  control:
    basis: providers earning contract_present + documentation_present + api_reference_present, minus the
      cohort
    n: 5216
  metric: >-
    cohort_pct / control_pct = mean share of the check's points earned (derived and platform credit weighted),
    x100
  measured_on: '2026-09-25'
  status: 'not measurable: 0 detected customers clear the baseline (need 20)'
simulation:
  simulated_on: '2026-09-25'
  rubric: 0.23.0
  population: providers publishing a contract (contract_present earned), replayable exactly
  providers: 8977
  providers_unreplayable: 987
  providers_moved: 0
  conditional_rows: excluded (they depend on what the API already does)
  composite_lift:
    median: 0.0
    p75: 0.0
    p90: 0.0
    max: 0.0
    mean_among_movers: 0.0
  agent_readiness_lift:
    median: 0.0
    p75: 0.0
    p90: 0.0
    max: 0.0
    mean_among_movers: 0.0
  facet_lift_median_among_movers: {}
  composite_band_moves: {}
  agent_readiness_band_moves: {}
  method: >-
    each provider's own kin/checks file, the vendor's maps at their stated credit, the scorer's composite
    formula; from -> to, nothing written