Automation discovery: search Zapier's app directory and find popular Zap templates between apps.
An MCP server for automation discovery. Zapier MCP executes automations — this server answers the question that comes first: what could I automate?
Sibling project: zapier-dev-mcp for building Zapier integrations.
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).
| 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 |
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.Not affiliated with or endorsed by Zapier.
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
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y zapier-discovery-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-arose26-zapier-discovery-mcp": {
"command": "npx",
"args": [
"-y",
"zapier-discovery-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencezapier-discovery-mcpnpmio.github.arose26/zapier-discovery-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.