English Français العربية

io.github.arose26/zapier-dev-mcp

Registre officiel Outils de développement

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

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package zapier-dev-mcp
Claude Code 
claude mcp add zapier-dev-mcp -- npx -y zapier-dev-mcp@0.2.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "zapier-dev-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "zapier-dev-mcp@0.2.0"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. zapier-dev-mcp
  2. Quick start
  3. Tools
  4. What the linter checks
  5. Notes
  6. Development
  7. License

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

Questions fréquentes

Qu'est-ce que io.github.arose26/zapier-dev-mcp ?

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

Comment installer io.github.arose26/zapier-dev-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add zapier-dev-mcp -- npx -y zapier-dev-mcp@0.2.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.arose26/zapier-dev-mcp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.arose26/zapier-dev-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.arose26/zapier-dev-mcp ?

Il est publié par arose26. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.