MCP Gateway · OpenCode
Connect Klaviyo to OpenCode
Quick numbers, like yesterday's orders or how many profiles opened an email, shouldn't need a dashboard. With Klaviyo configured as a remote server, OpenCode answers them in the terminal session you already have open. Speakeasy's OpenCode plugin approves or rejects every request first and reports token and cost totals per turn.
- Category
- Sales & CRM
- Tools
- 27
- Authentication
- OAuth
- OpenCode
- 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 OpenCode 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. OpenCode connects to the Klaviyo server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Klaviyo from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Klaviyo
Count events for a metric
Ask OpenCode for the count or unique profiles behind a metric over a date range, grouped by flow or campaign. It reports by event time, not send date.
Confirm which account you're on
Before a script writes profiles to Klaviyo, have OpenCode read the account details so you know it is connected to the production account and not a test one.
Inspect a segment definition
When a script's audience count looks off, OpenCode lists the account's segments and fetches the one in question to check it is the segment you meant.
Tools
27 tools
Each Klaviyo tool can be allowed or denied per team and role at the MCP Gateway before OpenCode 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 OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
Can OpenCode get Klaviyo from a plugin?
Where does OpenCode's usage data for Klaviyo come from?
How do OpenCode users get Klaviyo?
Are Klaviyo calls from OpenCode logged?
Connect more