MCP Marketplace
Sign inSign up
Back to Browse

Zapier Dev MCP Server

by Arose26
ProductivityModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-designed MCP server for Zapier integration developers with solid security practices. Authentication and authorization are not applicable (the server is a local development tool with no external auth). Code quality is high with proper input validation, error handling, and no dangerous patterns. The server appropriately uses child process execution with timeouts and output caps, avoids shell injection, and handles user input safely. Minor code quality observations exist but do not materially impact security. Supply chain analysis found 2 known vulnerabilities in dependencies (2 critical, 0 high severity). Package verification found 1 issue.

7 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

process_spawn

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub 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 mcp add zapier-dev -- npx -y zapier-dev-mcp

Claude 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."

Tools

ToolWhat it does
inspect_integrationStructured summary of the app definition
lint_integrationReview-readiness report: errors / warnings / info, each anchored to a component path
generate_test_fixturesReady-to-run bundle mocks (typed inputData, authData from your auth fields) plus an appTester test skeleton per component
validate_integrationRuns 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

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

Reviews

No reviews yet

Be the first to review this server!

More Productivity MCP Servers

Memory

Free

by Modelcontextprotocol · Productivity

Knowledge graph-based persistent memory across sessions

85.9K
Stars
26
Installs
8.0
Security
No ratings yet
Local

Time

Free

by Modelcontextprotocol · Productivity

Time and timezone conversion capabilities for your AI assistant

80.0K
Stars
3
Installs
9.5
Security
No ratings yet
Local

Toleno

Free

by Toleno · Developer Tools

Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.

180
Stars
632
Installs
8.0
Security
4.7
Local

mcp-creator-python

Free

by mcp-marketplace · Developer Tools

Create, build, and publish Python MCP servers to PyPI — conversationally.

-
Stars
104
Installs
10.0
Security
4.7
Local

MarkItDown

Free

by Microsoft · Content & Media

Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption

168.6K
Stars
74
Installs
4.2
Security
5.0
Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.

-
Stars
69
Installs
10.0
Security
5.0
Remote
Zapier Dev MCP Server - For Zapier integration developers: inspect, lint, and | MCP Marketplace