MCP Gateway · Cursor
Connect Klaviyo to Cursor
Signup forms and preference centers write straight into Klaviyo profiles and subscriptions. Cursor's agent can create a test profile against the real account and confirm what your form code actually stored, all from the editor. If Speakeasy hasn't approved a Klaviyo tool call, Cursor's hooks fail closed and the call never runs.
- Category
- Sales & CRM
- Tools
- 27
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Klaviyo MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Klaviyo call inspected and logged.
Set up
Add Klaviyo to Cursor in 4 steps
- 01
Add Klaviyo from the catalog
An admin finds Klaviyo 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.
Klaviyo uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
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.
- 02
Choose who can use Klaviyo
Give teams the
mcp:connectscope on the Klaviyo server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Klaviyo to their gateway on the next call, and removing it takes it away. - 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.
- 04
Sign in and use Klaviyo from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Klaviyo needs its own OAuth grant, so each person connects it once. Until they do, Klaviyo calls fail while the rest of the gateway keeps working.
From then on, Klaviyo'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 Klaviyo
Test a signup form end to end
Cursor subscribes a test email to marketing on the right channel, then reads the profile back to confirm its subscription details match what the form should produce.
Seed profiles for local testing
Create a few profiles with an email, phone number or external ID, and update their properties to cover the edge cases your preference center needs to handle.
Check list IDs used in code
Cursor looks up the lists in the account and their tags, so the list ID hard-coded in your form handler points at the list marketing expects.
Tools
27 tools
Each Klaviyo tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
klaviyo_get_account_details
Get the details of the account. You can view and edit your account details flow in the Klaviyo UI at https://www.klaviyo.com/settings/account
klaviyo_get_campaigns
Returns some or all campaigns based on filters. com/campaign/{CAMPAIGN_ID}/wizard. Do not use this for queries related to the status of campaigns, reporting on campaigns, or campaign performance data. For those use cases, use the get_campaign_report tool.
klaviyo_get_campaign
Returns a specific campaign based on a required id. You can view and edit a campaign in the Klaviyo UI at https://www.klaviyo.com/campaign/{CAMPAIGN_ID}/wizard
klaviyo_create_campaign
Creates a new draft campaign. For email campaigns, this can be used with the create_email_template tool for template creation and then assign_template_to_campaign_message to assign the template to the email campaign.
klaviyo_assign_template_to_campaign_message
Assigns an email template to a campaign message. This should be used after creating a template with the create_email_template tool and creating an email campaign.
klaviyo_get_flows
Returns some or all flows based on filters. com/flow/{FLOW_ID}/edit. Do not use this for queries related to the status of flows, reporting on flows, or flow performance data. For those use cases, use the get_flow_report tool.
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 Klaviyo call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Klaviyo tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Klaviyo 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
What happens when Speakeasy can't reach a decision for a Klaviyo call in Cursor?
Do I need to reload Cursor after the Klaviyo plugin changes?
How do Cursor users get Klaviyo?
Are Klaviyo calls from Cursor logged?
Connect more