Schema | zapier-dev-mcp

zapier-dev-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
inspect_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).
lint_integrationA	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`.
generate_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.
validate_integrationA	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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arose26/zapier-dev-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server