n8n MCP Server vs Zapier MCP

When to pick n8n MCP Server

• You are building an n8n workflow and need exact node properties, operations, or configuration examples. search_nodes finds nodes, while get_node returns schemas and documentation the model can use when writing configuration.
• You want to check generated configuration before saving it. validate_node checks individual nodes, and validate_workflow checks the assembled workflow, including connections and expressions. This fits development work where the agent needs to revise its output after validation errors.
• You already operate an n8n instance and want the agent to create workflows, apply partial updates, or inspect executions. These management tools use your configured n8n API connection.
• You want to start from an existing workflow template. search_templates supports searches by task, node, or metadata, and get_template retrieves workflow JSON for inspection and adaptation.

When to pick Zapier MCP

• You want an agent to act across apps already connected to your Zapier account. Meeting preparation using Calendar, Gmail, and Salesforce is a documented example of work that spans those connections.
• You want Zapier to manage app credentials and restrict which apps and actions agents can use. Credentials stay in Zapier's connection layer, and MCP action History records what ran.
• You need to reach an internal API or transform data when a standard action does not fit. Zapier documents Code Actions that let the agent write and execute code for those cases.
• You want to reuse a process developed in chat. Zapier supports saving workflows as Skills; building and deploying Next Gen Zaps from supported clients is described as early access.

Main differences

• The work targets different objects. n8n MCP Server exposes node schemas, templates, validation, and workflow management. Zapier MCP discovers and executes app actions, so choose according to whether you are editing an n8n workflow or asking an agent to work across connected apps.
• Deployment differs. n8n MCP Server offers a local Node process, self-hosted deployment, and a hosted service, with local and HTTP transport options. Zapier MCP connects your client to Zapier's hosted HTTP endpoint.
• Authentication depends on the task. n8n documentation tools can be used without an n8n API connection; instance management requires N8N_API_URL and N8N_API_KEY. Its hosted service uses an API key. Zapier MCP requires authentication and uses app connections authorized in Zapier.
• Access controls take different forms. n8n MCP Server supports DISABLED_TOOLS and DISABLED_TOOL_OPERATIONS to remove tools or block operations. Zapier manages app and action permissions centrally. Its page describes action discovery, while the supplied directory facts describe explicitly enabled actions, so confirm the available action-selection flow during setup.
• Execution and data routing follow the deployment. n8n management requests go to the configured n8n instance; running the MCP process locally does not make those requests local. Zapier executes actions through its managed app connections and keeps app credentials outside the model.

Setup

For n8n MCP Server, use npx -y n8n-mcp to start the local server and configure your MCP client to launch it. Add N8N_API_URL and N8N_API_KEY for instance management. Features such as node resource discovery also require the separate N8N_MCP_ACCESS_TOKEN from n8n's instance-level MCP settings.

For Zapier MCP in Claude Code, run claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect. Authenticate, choose the connected apps the agent may access, and review action permissions. Zapier manages the app connections used when the agent executes an action.