MCP Gateway · Claude
Connect Klaviyo to Claude
Email marketers spend much of their week comparing campaign results and setting up the next send. Once Klaviyo is a connector in Claude, they can ask for performance numbers in plain language and have a draft campaign started for them. Speakeasy shows each marketer only the servers and tools their role is approved for.
- Category
- Sales & CRM
- Tools
- 27
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
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 Claude 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 Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Klaviyo from Claude
The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Klaviyo
Compare last month's campaigns
Ask Claude for opens, clicks and conversions on last month's campaigns, with the audiences each was sent to, and get the three that performed best.
Start a draft campaign
Describe the next promotion and Claude creates a draft email campaign, builds a template from its HTML and assigns it to the message for you to review in Klaviyo.
klaviyo_create_campaignklaviyo_create_email_templateklaviyo_assign_template_to_campaign_message
Review a past campaign's setup
Before reusing an idea, ask Claude to find an earlier campaign by name and summarize how it was set up, so you can decide what to keep for the next one.
Tools
27 tools
Each Klaviyo tool can be allowed or denied per team and role at the MCP Gateway before Claude 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 Claude
The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Who adds Klaviyo to Claude for a Team or Enterprise organization?
Can Claude's Klaviyo prompts be blocked before inference?
How do Claude users get Klaviyo?
Are Klaviyo calls from Claude logged?
Connect more