Skip to main content
Back to the Zapier MCP server

MCP Gateway · Cursor

Zapier icon

Connect Zapier to Cursor

While you work in the editor, Zapier MCP can stand in for apps your project touches but doesn't integrate directly, using actions set up on Zapier's side. Cursor can bring up the page that manages those actions whenever the set needs adjusting. The Speakeasy gateway logs each Zapier call with the developer's email, and Cursor hooks check every prompt and tool call before it runs.

Category
Productivity
Tools
1
Cursor
Editor and terminal

Behind the MCP Gateway

Run Zapier MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Zapier call inspected and logged.

Deploy on MCP Gateway

Before you start

What Zapier needs first

No admin needed; the Zapier account manager only if MCP is disabled does the Zapier side of the setup.

  • Zapier MCP is available on every Zapier plan.
  • If Zapier MCP is disabled, the Zapier account manager must enable it for the workspace.
  • You do not need an app connection to establish the MCP connection.
Full Zapier setup guide in the docs

Set up

Add Zapier to Cursor in 4 steps

  1. 01

    Add Zapier from the catalog

    An admin finds Zapier in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Zapier

    Give teams the mcp:connect scope on the Zapier server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Zapier to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Zapier from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Zapier's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Zapier

Open action settings from the editor

Ask Cursor where the Zapier actions are configured. It returns the link, so you can adjust the available actions without searching through Zapier's settings yourself.

get_configuration_url

Add an action a feature needs

While building a feature that has to notify or update another app, get the configuration URL from Cursor and add the action before wiring it into your code.

get_configuration_url

Review the action list during code review

When reviewing a change that depends on Zapier, Cursor fetches the configuration page so the reviewer can confirm which actions the change expects.

get_configuration_url

Tools

1 tool

Each Zapier tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.

get_configuration_url

Returns the URL where users can configure this MCP server - adding, editing, or removing actions. Provide this URL to users who want to customize their available tools.

Control

What Speakeasy can see and stop in Cursor

The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.

Tool logs

Gateway

Every Zapier call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Zapier tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Zapier can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Who has to enable Zapier MCP before Cursor can use it?
No admin is needed in most cases. If Zapier MCP is disabled for the workspace, the Zapier account manager must enable it.
Do Cursor Cloud agents get the same Zapier controls?
Cursor Cloud agents need a checked-in .cursor/hooks.json, and session and MCP-specific hooks don't run there.
How do Cursor users get Zapier?
An admin adds Zapier from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Zapier tools their access allows.
Are Zapier calls from Cursor logged?
Yes. Zapier calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Zapier in other clients

AI everywhere.

Control here.