MCP Gateway · Codex
Connect Klaviyo to Codex
Email templates are code too, and many teams keep their HTML in a repository. Codex can build a template from that source and create it in Klaviyo, ready for a marketer to pick up. Klaviyo sits behind the organization gateway, so Codex never holds a Klaviyo credential, and Speakeasy's hooks can stop any tool call it makes.
- Category
- Sales & CRM
- Tools
- 27
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
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 Codex 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 Codex
Add the gateway as an MCP server, then log in.
Run the first command with your organization gateway URL.
Run the second command to sign in.
codex mcp add 'speakeasy' \ --url 'https://<organization host>/mcp/gateway/<organization slug>' codex mcp login 'speakeasy' - 04
Sign in and use Klaviyo from Codex
The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Use cases
What Codex users do with Klaviyo
Ship a template from the repo
Codex renders the email HTML from your template source and creates it as a new Klaviyo email template, then returns the template ID for the marketing team.
Upload the images it references
Before creating the template, Codex uploads each hosted image or data URI to Klaviyo, so the email doesn't depend on links that may change.
Diff a live template against source
Codex fetches an existing template's HTML from Klaviyo and compares it with the version in the repo, so hand edits in the Klaviyo UI don't get overwritten unnoticed.
Tools
27 tools
Each Klaviyo tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex
The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Codex
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
User attribution
Codex
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
Budgets
Codex
Spend limits can block Codex traffic once a budget is reached.
Device agent and MDM
Codex
The device agent keeps Codex's configuration in sync on managed laptops.
- Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
- The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
Is Klaviyo usage from Codex counted against a budget?
Can Codex send a Klaviyo campaign?
How do Codex users get Klaviyo?
Are Klaviyo calls from Codex logged?
Connect more