About zapier-discovery-mcp
zapier-discovery-mcp is an MCP server for exploring automation ideas through Zapier's app directory and popular Zap templates. It helps people identify supported apps and discover templates ranked by actual usage.
Key features
- 01Search the Zapier app directory
- 02Find popular templates for one app or an app pair
- 03Return template step chains and descriptions
- 04Provide one-click template creation links
Use cases
- 01Check whether a tool has a Zapier integration
- 02Explore common automations between two apps
- 03Find usage-ranked automation ideas for a CRM
MCP support
Exposes app search and Zap template discovery tools to MCP clients through the Zapier Partner API. It requires a Zapier Partner API client_id.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y zapier-discovery-mcpZAPIER_CLIENT_IDZapier Partner API client_id (free with any Zapier integration; see docs.api.zapier.com)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
2Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Max results |
| query | string | No | App name to search for, e.g. 'notion' |
Details
From the project READMEzapier-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
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:
{
"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
| Tool | What it does |
|---|---|
search_apps | Search the app directory by name; popularity-ordered without a query. Returns slugs for the next step. |
find_zap_templates | Popular 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. MissingZAPIER_CLIENT_IDproduces 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
npm install
npm 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.