Zapier MCP server for Claude, Codex and Cursor

What your AI apps can do with Zapier

Run configured app actions
Connect apps without separate servers

Zapier MCP tools

16 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`inspect_zapier_actions`	Lists your enabled actions and what each needs to run
`discover_zapier_actions`	Searches apps and actions you could add
`enable_zapier_action`	Enables an action as a callable tool
`disable_zapier_action`	Removes an action you no longer need
`auto_provision_mcp`	Enables actions from your existing Zapier app connections
`execute_zapier_read_action`	Runs a read or search action, such as finding a contact
`execute_zapier_write_action`	Runs a write action, such as sending a message or updating a record
`list_zapier_connections`	Lists the app connections available for an app
`manage_zapier_connections`	Returns a link to add a connection, or sets an app's default connection
`get_configuration_url`	Returns the link to your Zapier MCP configuration page
`list_zapier_skills`	Lists saved skills or reads one
`get_zapier_skill`	Lists saved skills or reads one
`create_zapier_skill`	Creates or edits a reusable skill
`update_zapier_skill`	Creates or edits a reusable skill
`delete_zapier_skill`	Deletes a skill
`send_feedback`	Sends feedback to Zapier

Suggested access for each AI app

The documentation this list comes from doesn't mark Zapier's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Zapier connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Zapier to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Zapier tool, give Cursor only the read tools, or keep Zapier away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Zapier MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Zapier in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Zapier endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http zapier 'https://mcp.zapier.com/api/mcp/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "zapier": {
      "url": "https://mcp.zapier.com/api/mcp/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Zapier MCP documentation for what your client needs.

Before you connect

A Zapier account. Choose which actions Zapier exposes in its MCP settings.

Server details

Detail	Value
Publisher	Zapier
Endpoint	`https://mcp.zapier.com/api/mcp/mcp`
Authentication	Browser sign-in
Categories	Productivity
Tool list	16 tools, observed 29 October 2026 (docs)

Zapier MCP documentation