Skip to main content
Back to the Klaviyo MCP server

MCP Gateway · Claude Code

Klaviyo icon

Connect Klaviyo to Claude Code

When a storefront sends events to Klaviyo, the hardest bugs are the ones where an event arrives with the wrong name or missing properties. With Klaviyo behind the Speakeasy MCP Gateway, Claude Code can check the metrics and raw events a test profile produced while the tracking code is open. Agent hooks check each tool call first.

Category
Sales & CRM
Tools
27
Authentication
OAuth
Claude Code
CLI

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.

Deploy on MCP Gateway

Set up

Add Klaviyo to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use Klaviyo

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Klaviyo from Claude Code

    The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Klaviyo

Verify a tracking event landed

After triggering a checkout in staging, Claude Code looks up the metric for it and inspects the individual events recorded for your test profile, property by property.

klaviyo_get_metricsklaviyo_get_eventsklaviyo_get_profile

See which flows a rename affects

Before renaming an event in code, Claude Code lists the account's flows and pulls a flow report with each one's trigger type, so a refactor doesn't silently stop an email.

klaviyo_get_flowsklaviyo_get_flow_report

Check the product catalog matches

Claude Code pulls the catalog items Klaviyo holds and compares them with the products your code sends, flagging items that are missing or out of step.

klaviyo_get_catalog_items

Tools

27 tools

Each Klaviyo tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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.

See all 27 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can Claude Code unsubscribe Klaviyo profiles?
Only if the person's role allows klaviyo_unsubscribe_profile_from_marketing. Each of the 27 Klaviyo tools can be allowed or denied per team at the MCP Gateway, and agent hooks let Speakeasy deny a call before Claude Code runs it.
Can Klaviyo work in Claude Code on the web?
Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
How do Claude Code users get Klaviyo?
An admin adds Klaviyo from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Klaviyo tools their access allows.
Are Klaviyo calls from Claude Code logged?
Yes. Klaviyo 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

Klaviyo in other clients

AI everywhere.

Control here.