zapier-dev-mcp
Provides tools for developing and reviewing Zapier integrations, including inspecting app definitions, linting for review readiness, generating test fixtures, and running validation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zapier-dev-mcp Lint C:\code\my-zapier-app and walk me through fixing the errors."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
zapier-dev-mcp
An MCP server for people who build Zapier integrations. Zapier MCP lets AI use Zapier apps — this server helps you ship one. Point Claude at your zapier-platform-cli project:
"What's in this integration?" — triggers, creates, searches, auth, platform version, request hooks
"Is it ready for app review?" — a lint pass encoding the things Zapier's review commonly bounces integrations for
"Run the validator" — wraps your project's own
zapier validate
Quick start
Claude Code
claude mcp add zapier-dev -- npx -y zapier-dev-mcpClaude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"zapier-dev": {
"command": "npx",
"args": ["-y", "zapier-dev-mcp"]
}
}
}Then: "Lint C:\code\my-zapier-app and walk me through fixing the errors."
Related MCP server: MCP Spectral
Tools
Tool | What it does |
| Structured summary of the app definition |
| Review-readiness report: errors / warnings / info, each anchored to a component path |
| Ready-to-run bundle mocks (typed |
| Runs the project's own |
What the linter checks
Missing
operation.sampleon visible actions — required for public apps, and the single most common review bounceDynamic dropdowns (
"trigger_key.id.label") referencing triggers that don't existMissing
display.label/display.description/noun; unlabeled input fieldsDefinition
versionvspackage.jsonversion mismatch;platformVersionvs thezapier-platform-coredependencyAuth without a
connectionLabel(users can't tell accounts apart)Key/map-key mismatches and duplicate keys
hidden components skip the visibility checks. The linter complements zapier validate — schema validation catches malformed definitions; this catches reviewable-but-rough ones.
Notes
Inspecting a project evaluates its entry module in a child process (with a timeout and output cap) — exactly what the Zapier CLI itself does. Only point it at projects you trust, i.e. your own.
Computed input fields (functions) can't be linted statically; they're skipped, not flagged.
Not affiliated with or endorsed by Zapier.
zapier-platform-cliis Zapier's open-source SDK.
Development
npm install
npm test # offline tests — synthetic projects written in-suite
npm run build # tsc → dist/
node scripts/smoke.mjs # end-to-end: generates a project, drives the server over stdioArchitecture: src/extract.ts (definition extraction via child process) and src/lint.ts (pure review checks) carry the logic; src/index.ts is the MCP wiring.
License
MIT
Available Tools
4 toolsgenerate_test_fixturesGenerate test fixturesA
Ready-to-run test scaffolds for the integration: a bundle mock (authData from the auth fields, typed inputData from each component's input fields) plus a zapier-platform appTester test skeleton per trigger/create/search. Optionally target one component.
Inputs: path (required), component.
inspect_integrationInspect a Zapier integrationA
Structured summary of a zapier-platform-cli project: triggers, creates, searches, authentication, platform version, request hooks. Note: this evaluates the project's own entry module (exactly as the Zapier CLI does).
Inputs: path (required).
lint_integrationLint for review readinessA
Checks a Zapier integration against common app-review blockers: missing sample data, unlabeled input fields, missing descriptions/nouns, dynamic dropdowns referencing nonexistent triggers, version mismatches. Complements (does not replace) zapier validate.
Inputs: path (required).
validate_integrationRun zapier validateA
Runs the project's own zapier validate (schema + style checks) via npx. Requires zapier-platform-cli in the project or globally; returns install guidance if missing.
Inputs: path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clear primary purpose: generating fixtures, inspecting, linting, and validating. However, lint_integration and validate_integration are both quality checks, and an agent might need to read descriptions carefully to pick the right one.
All tool names follow a consistent verb_noun pattern in snake_case: generate_test_fixtures, inspect_integration, lint_integration, validate_integration. The verbs clearly indicate actions and nouns uniformly refer to integration artifacts.
Four tools is a well-scoped set for a Zapier development helper. Each tool covers a distinct phase (generate, inspect, lint, validate) without redundant utilities, fitting the recommended 3-15 range.
The set covers the core lifecycle for integration quality: generating test fixtures, inspecting structure, linting for blockers, and running official validation. A notable gap is the lack of a tool to execute tests or apply fixes, but the surface is reasonably complete for analysis tasks.
Maintenance
Related MCP Connectors
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
MCP Spec Compliance MCP — audits any MCP server.json against the official Model Context Protocol
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that validates LLM-generated tool-call arguments, lints tool definitions, and produces retry messages for AI assistants.352 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps Spectral to lint OpenAPI specifications, enabling LLMs to validate and fix API definitions.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides code validation rules and analysis for various stacks/frameworks, enabling automated code reviews and reporting directly from VS Code and other editors.-
- AlicenseAqualityDmaintenanceA stdio MCP server that audits other MCP servers by linting their tool schemas and calling tools with malformed inputs to produce a 0–100 conformance score and Markdown report.614 npmMIT