zapier-discovery-mcp
MCP server for automation discovery, enabling users to search Zapier's app directory for integrations and find popular ready-made Zap templates with one-click create links.
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
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.