Zapier Discovery Mcp

io.github.arose26Published by GitHub account arose26v0.1.0Updated Oct 24, 2026

Automation discovery: search Zapier's app directory and find popular Zap templates between apps.

The publisher's own server: Zapier

VerifiedSTDIODesktop onlyProductivity & WorkflowWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant search Zapier's app directory and find popular ready-made Zap templates between apps.

What you can do
This server provides automation discovery rather than execution. Its search_apps tool looks up apps in Zapier's directory by name, ordered by popularity when no query is given, and returns slugs for follow-up calls. Its find_zap_templates tool returns popular ready-made Zap templates for one app or a pair, including title, step chain, description, and a one-click create link.
When to use it
Use it when someone asks what can be automated between two tools, whether a given product has a Zapier integration, or wants automation ideas for a system such as a CRM. It answers the discovery question before any automation is built or run.
Requirements
Runs locally over stdio, typically via npx from the npm package zapier-discovery-mcp, so Node.js is needed. It requires a Zapier Partner API client_id supplied through the ZAPIER_CLIENT_ID environment variable; the README says this is free with any Zapier integration and is not a secret. Network access to the Zapier Partner API is required, and ZAPIER_API_BASE can override the API host.
Before you install
The only credential requested is ZAPIER_CLIENT_ID, described as a non-secret client id rather than a private key. The server is read-only discovery: it searches the app directory and returns template links, and does not create, run, or modify automations. Queries are sent to Zapier's Partner API, and the README notes the project is not affiliated with or endorsed by Zapier.

Installation

In SourceWeft

  1. Open Zapier Discovery Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

zapier-discovery-mcp

An MCP server for automation discovery. Zapier MCP executes automations — this server answers the question that comes first: what could I automate?

  • "What do people automate between Slack and Notion?" — real, popular Zap templates, each with a one-click create link
  • "Is there a Zapier integration for this tool?" — search the 9,000+ app directory
  • "Give me automation ideas for my CRM" — templates ranked by actual usage, not hallucinated

Sibling project: zapier-dev-mcp for building Zapier integrations.

Setup

You need a Zapier Partner API client_id — free with any Zapier integration, and not a secret (it ships in client-side embed code). See the Partner API docs for where to find yours.

Claude Code

bash
claude mcp add zapier-discovery --env ZAPIER_CLIENT_ID=your_client_id -- npx -y zapier-discovery-mcp

Claude Desktop — add to claude_desktop_config.json:

json
{  "mcpServers": {    "zapier-discovery": {      "command": "npx",      "args": ["-y", "zapier-discovery-mcp"],      "env": { "ZAPIER_CLIENT_ID": "your_client_id" }    }  }}

Optional: ZAPIER_API_BASE overrides the API host (testing, proxies).

Tools

ToolWhat it does
search_appsSearch the app directory by name; popularity-ordered without a query. Returns slugs for the next step.
find_zap_templatesPopular ready-made Zap templates for one app or a pair — title, step chain (Slack → Notion), description, one-click create URL

Design notes

  • Defensive parsing. Partner API responses are only partially documented; the client whitelists fields and handles both bare-array and enveloped responses rather than assuming shapes.
  • Testable without credentials. The smoke test runs a local HTTP mock of the Partner API and points the server at it via ZAPIER_API_BASE — full end-to-end over stdio with zero secrets. Missing ZAPIER_CLIENT_ID produces setup instructions as a tool error, not a crash.
  • HTML in titles/descriptions is stripped and truncated before it reaches the model.

Not affiliated with or endorsed by Zapier.

Development

bash
npm installnpm test                 # offline unit tests (mocked fetch)npm run build            # tsc → dist/node scripts/smoke.mjs   # end-to-end against a local Partner API mock

License

MIT

Source: README.md at commit 37946a6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Zapier integrations

Zapier

com.zapierOfficial publisher

Hosted Zapier MCP server that lets an AI assistant act across 9,000+ apps and 40,000+ actions, such as sending messages, pulling data and triggering workflows.

Streamable HTTPWeb executableAuth
Productivity & WorkflowCredential requiredNov 2, 2026

Zapier Dev Mcp

Published by GitHub account arose26

A local MCP server that lets an assistant inspect, lint and validate zapier-platform-cli integration projects before Zapier app review.

STDIODesktop only
Productivity & WorkflowNot validated yetOct 24, 2026