Zapier Dev Mcp

io.github.arose26Published by GitHub account arose26v0.2.0Updated Oct 24, 2026

For Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects.

The publisher's own server: Zapier

VerifiedSTDIODesktop onlyProductivity & Workflow Developer Tools

Server details

Identifier: io.github.arose26/zapier-dev-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account arose26 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.arose26%2Fzapier-dev-mcp.svg)](https://sourceweft.com/mcp/io.github.arose26%2Fzapier-dev-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant inspect, lint and validate zapier-platform-cli integration projects before Zapier app review.

What you can do: Inspect a Zapier integration project and summarize its triggers, creates, searches, auth, platform version and request hooks from the app definition. Lint the project for review-readiness, reporting errors, warnings and info anchored to component paths, covering missing samples, broken dynamic dropdown references, missing labels, version mismatches, missing connection labels and key mismatches. Generate test fixtures: typed inputData and authData mocks plus an appTester test skeleton per component. Run the project's own zapier validate for schema and style checks, with install guidance if the CLI is missing.
When to use it: Useful when you are building or maintaining a Zapier integration with zapier-platform-cli and want an assistant to explain the app's structure, catch common app-review problems, scaffold tests, or run the validator without leaving the conversation.
Requirements: Runs locally over stdio, typically launched with npx from the npm package zapier-dev-mcp, so Node.js and network access for the package are needed. The target project should be a zapier-platform-cli project; running the validator requires the project's own zapier CLI to be installed. No accounts, API keys or environment variables are declared.

Before you install

Inspecting a project evaluates its entry module in a child process, so only point it at projects you trust, such as your own. Computed input fields defined as functions are skipped rather than linted. The linter complements but does not replace zapier validate. The server is not affiliated with or endorsed by Zapier.

Installation

In SourceWeft

Open Zapier Dev Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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 Desktop — add to claude_desktop_config.json:

json

{  "mcpServers": {    "zapier-dev": {      "command": "npx",      "args": ["-y", "zapier-dev-mcp"]    }  }}

{  "mcpServers": {    "zapier-dev": {      "command": "npx",      "args": ["-y", "zapier-dev-mcp"]    }  }}

Then: "Lint C:\code\my-zapier-app and walk me through fixing the errors."

Tools

Tool	What it does
`inspect_integration`	Structured summary of the app definition
`lint_integration`	Review-readiness report: errors / warnings / info, each anchored to a component path
`generate_test_fixtures`	Ready-to-run bundle mocks (typed `inputData`, `authData` from your auth fields) plus an appTester test skeleton per component
`validate_integration`	Runs the project's own `zapier validate` (schema + style), with install guidance if the CLI is missing

What the linter checks

Missing operation.sample on visible actions — required for public apps, and the single most common review bounce
Dynamic dropdowns ("trigger_key.id.label") referencing triggers that don't exist
Missing display.label / display.description / noun; unlabeled input fields
Definition version vs package.json version mismatch; platformVersion vs the zapier-platform-core dependency
Auth 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-cli is Zapier's open-source SDK.

Development

bash

npm installnpm test                 # offline tests — synthetic projects written in-suitenpm run build            # tsc → dist/node scripts/smoke.mjs   # end-to-end: generates a project, drives the server over stdio

npm installnpm test                 # offline tests — synthetic projects written in-suitenpm run build            # tsc → dist/node scripts/smoke.mjs   # end-to-end: generates a project, drives the server over stdio

Architecture: 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

Source: README.md at commit 57d7f08

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Zapier integrations

Zapier

com.zapierOfficial publisher

Hosted Zapier MCP server that lets an AI assistant act across 9,000+ apps and 40,000+ actions, such as sending messages, pulling data and triggering workflows.

Streamable HTTPWeb executableAuth

Productivity & WorkflowCredential requiredNov 2, 2026

Zapier Discovery Mcp

Published by GitHub account arose26

Lets an assistant search Zapier's app directory and find popular ready-made Zap templates between apps.

STDIODesktop only

Productivity & WorkflowNot validated yetOct 24, 2026