By Moahashem
Generic Zapier MCP proxy. Exposes the Zapier action surface (Gmail, Slack, Sheets, GitHub, Calendar, and 7000+ other apps) as MCP tools via Zapier's meta-tool API pattern.
Model Context Protocol server that proxies Zapier MCP over stdio with per-agent identity and optional tool filtering. Companion to
leadsimple-mcp— same architecture, no app-specific filter.
Zapier already ships a remote MCP server at mcp.zapier.com. So why a wrapper?
ZAPIER_MATCH_TERMS=gmail,slack,sheets narrows the agent's toolbox without re-configuring the upstream server.ZAPIER_TOOL_PREFIX=zapier_ keeps tool names clearly tagged in the agent's UI.If you only want LeadSimple actions, use leadsimple-mcp — it's the same proxy with a LeadSimple-shaped filter baked in.
Open mcp.zapier.com, create a server, add the actions you want this agent to have, then grab the URL from the Connect tab. It looks like https://mcp.zapier.com/api/mcp/s/<long-token>/mcp and contains an embedded token — treat it like a password.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"zapier": {
"command": "npx",
"args": ["-y", "zapier-mcp-proxy"],
"env": {
"ZAPIER_MCP_URL": "https://mcp.zapier.com/api/mcp/s/..."
}
}
}
}
claude mcp add zapier -- env ZAPIER_MCP_URL=https://mcp.zapier.com/api/mcp/s/... npx -y zapier-mcp-proxy
"Use Zapier to send a Slack message to #general saying we just shipped the LeadSimple MCP."
| Env var | Required | Default | Purpose |
|---|---|---|---|
ZAPIER_MCP_URL | yes | — | Your Zapier MCP server URL from mcp.zapier.com. |
ZAPIER_MATCH_TERMS | no | `` (empty = pass-through) | Comma-separated substrings. Tool name OR description must contain at least one to be exposed. |
ZAPIER_TOOL_PREFIX | no | `` | Prefix added to every exposed tool name. Set to zapier_ for explicit tagging. |
ZAPIER_KEEP_META_TOOLS | no | true | Whether to keep Zapier meta tools like get_configuration_url. Useful for self-service reconfiguration. |
ZAPIER_LOG_LEVEL | no | info | silent | error | warn | info | debug. |
ZAPIER_TIMEOUT_MS | no | 60000 | Per-request timeout against the upstream server. |
ZAPIER_MCP_URL=https://mcp.zapier.com/api/mcp/s/... npm run probe
Prints a side-by-side view of what the upstream server advertises vs. what would be exposed by this proxy under the current config.
git clone https://github.com/Moahashem/zapier-mcp.git
cd zapier-mcp
npm install
npm run typecheck
npm run build
ZAPIER_MCP_URL=https://mcp.zapier.com/api/mcp/s/... \
ZAPIER_LOG_LEVEL=debug \
npm run dev
MIT — see LICENSE.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
VestLaunch CRM MCP server — manifest-driven, multi-agent. Wraps the ffl-crm /api/v1/* surface so any MCP-compatible agent can read and (with explicit opt-in) write CRM data.
LeadSimple CRM MCP server. Wraps LeadSimple's API surface as MCP tools so any MCP-compatible agent can read and (with explicit opt-in) write LeadSimple data.
npx claudepluginhub moahashem/zapier-mcpHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Plugin that includes the Figma MCP server and Skills for common workflows