Skip to content
anlyon.devby Anlyon

Zapier MCP server

com.zapier/mcpzapier.comremotev1.0.1

Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.

No tools shown: it asks for sign-in first

This server lists its tools only to a signed-in client (OAuth). anlyon.dev never signs in or sends credentials, so it cannot read them, and nothing here is a judgement of the server. Already use it? Copy its tools/list from your client and check it here: the same labels, worked out in your browser.

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.

Compare with similar serversMarkdownJSONReport this listing

What the Zapier MCP server can do

The Zapier MCP server is published by zapier.com, a domain the MCP Registry verified. It asks for sign-in (OAuth) before it lists its tools, and anlyon.dev never signs in, so its tools are not shown.

Scan status: sign-in required

Scopes it asks for: email, openid, profile

Last attempt Nov 9, 2026, 19:17 UTC.

Have its tools/list output? Check it yourself.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 13, 2026, 11:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://mcp.zapier.com/.well-known/oauth-protected-resource/api/v1/connect
RFC 9728 protected resource metadata
https://mcp.zapier.com/.well-known/oauth-protected-resource/api/v1/connect
Authorization servers
https://mcp.zapier.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect
claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect

Run in a terminal.

Badge

A badge for your README that links back to this page.

Badge

anlyon.dev badge for com.zapier/mcp
[![anlyon.dev](https://anlyon.dev/badge/com.zapier/mcp.svg)](https://anlyon.dev/servers/com.zapier/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.

Zapier MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zapier MCP server safe?

anlyon.dev has not been able to list its tools, so it has no classes or findings for it yet. It asks for sign-in before listing them. Paste its tools/list output into https://anlyon.dev/scan to check it yourself.

Who publishes the Zapier MCP server?

zapier.com (domain verified by the MCP Registry).