Figma to Klaviyo MCP: Connect Claude to Klaviyo Template Creation

Carvr's MCP server exposes email-design analysis and Klaviyo template creation as tools any MCP-compatible AI assistant can call. Setup guide and current capabilities.

An AI-Callable Way to Slice and Push Email Designs to Klaviyo

The Carvr MCP is a Model Context Protocol server that exposes Carvr's design-analysis and Klaviyo-template-creation pipeline as tools an AI assistant can call directly. Instead of uploading an image in the web app or clicking a plugin button, you describe what you want to Claude (or another MCP-compatible client) and it calls the right tool with the right arguments.

It runs on the exact same backend as Carvr's public HTTP API — the MCP server is a thin protocol adapter, nothing more. Every tool call forwards to a real HTTP endpoint with your bearer token, so auth, billing, and rate limits work identically either way.

What Is MCP (Model Context Protocol)?

Model Context Protocol (MCP) is an open standard from Anthropic that lets AI assistants like Claude safely connect to external tools, data, and services. An MCP server exposes a set of tools (read a file, query a database, call an API) that an AI assistant can discover and call on your behalf.

Think of MCP as "USB for AI." Any compliant client (Claude Desktop, Claude Code, Cursor, or your own agent) can plug into any compliant server and immediately know how to use it — no custom integration code required.

What the Carvr MCP Actually Does

Five tools, each a thin wrapper over its public-API endpoint (the API's sixth endpoint, create-brand, is deliberately HTTP-only: an ESP API key shouldn't pass through an AI transcript):

• list_brands: the brands your API token can access, and the ESP each one is connected to.
• get_account_status: plan tier and remaining upload credits.
• analyze_email_design: send an image, get back suggested slice positions from Carvr's AI-guided slicer, plus an annotated preview image with the cut lines drawn on and numbered — useful for a human (or the AI, describing it back to you) to sanity-check before spending a credit.
• create_klaviyo_template: upload sections you've already cropped yourself and create the Klaviyo template. Bills one credit. Alt text is optional — leave it out and Carvr generates it with AI vision, the same pipeline the plugin uses.
• slice_and_upload (coming soon): the whole pipeline in one call — hand over a full, uncropped design image plus a brandId, and Carvr slices it, generates alt text, and uploads it to the brand's connected ESP (Klaviyo, Omnisend, or Mailchimp) in a single step. Also bills one credit. Until it ships, use analyze_email_design + create_klaviyo_template, which also let you inspect or adjust the slice positions before anything is cropped or billed.

Everything runs through the same battle-tested Carvr backend that already powers Figma-to-Klaviyo exports from the plugin and web app, so the output is identical in shape.

What the Carvr MCP Doesn't Do (Yet)

Three real gaps, each a deliberate scope decision rather than an oversight:

• It doesn't read Figma directly. There is no "pull the Summer Sale frame from my Figma file" tool. Carvr's MCP starts from an image you already have — exported from the Figma plugin, generated another way, or handed off from your own separate Figma MCP client-side. This is a deliberate architecture choice (composition, not integration): Carvr's server never needs to own Figma API logic.
• It doesn't map links from Figma prototype interactions. Each section's click-through link is a plain string you supply — nothing reads Figma's prototype data.
• It can't update an existing template — only create a new one. The internal web app has an update path (edit a template, keep the same Klaviyo ID); it just isn't exposed as a public tool yet.

None of these need a different architecture to add later — they're scope, not a wall.

Why Use AI + MCP for This

• Agencies running many brands: script a loop over brands from a single Claude conversation instead of repeating manual uploads.
• Working inside Claude Desktop or Claude Code already: keep template creation in the same place as the rest of your workflow instead of switching tools.
• Composing with other MCP servers: pair Carvr's MCP with a Figma MCP, project-management MCP, or your own agent to drive more of the pipeline end to end — Carvr handles the slice-and-create half.
• Scripted/CI use: the same five tools work over plain HTTP too (see the API Reference) if you'd rather not go through an AI client at all.

MCP vs. Plugin vs. Web App

Three ways to get from a design to a Klaviyo template — pick the one that fits:

• Figma plugin: fastest one-click send, reads the frame directly out of Figma. See the Figma plugin guide.
• Web app: upload a JPEG or PNG from any tool, slice and fine-tune visually. See the slicing guide.
• MCP server: drive analyze + create from Claude or any MCP-compatible client, in a conversation or a script — bring your own image.

Which AI Clients Work With the Carvr MCP?

Any client that speaks standard MCP over streamable HTTP, including:

• Claude Desktop (Anthropic).
• Claude Code: Anthropic's CLI agent.
• Cursor: the AI-first code editor.
• Custom agents built with the Claude Agent SDK or the Anthropic API.
• Any other MCP client — the protocol is open.

Connecting Your Client

Get a token from your Profile → API Tokens for AI Tools, then add the server to your client's config — the exact steps and copy-pasteable snippets for Claude Code, Claude Desktop, and Cursor are on the API Reference page. It's a URL and a bearer header; every MCP client takes those the same basic way.

Example Prompts

Once connected, these become natural conversation once you have an image ready:

• "Slice and upload this design straight to Klaviyo for brand XYZ — one shot, no need to check the cuts first."
• "Analyze this email design image and tell me where you'd slice it."
• "Create a Klaviyo template from these sections for the Summer Sale campaign, brand XYZ."
• "Check my remaining upload credits before we start a batch of five templates."
• "List my brands so I can pick the right one for this template."

Prompts implying Carvr reads Figma for you directly ("take the frame from my Figma file") aren't accurate yet — export the frame first (plugin, or your own Figma MCP), then hand the image to Carvr.

Authentication

• The same carvr_live_... bearer token from Profile authenticates both the HTTP API and the MCP server.
• Your ESP connections stay on Carvr's servers. The AI only ever sees your Carvr token, never your Klaviyo credentials.
• Revoke a token at any time from Profile → API Tokens; it stops working immediately, on both surfaces.
• Tokens can be scoped to specific brands, recommended for anything handed to a third-party tool or automation.

Pricing

Included on every Carvr plan at no extra cost, same as the Figma plugin. An MCP-initiated template creation counts the same as a plugin or web app upload against your plan's monthly credit allowance.

Related Reading

• API Reference: full endpoint docs, MCP client setup, and the underlying HTTP API.
• Figma Plugin Guide: one-click Figma-to-Klaviyo, including reading the frame directly.
• Web App: Slicing Emails: upload designs from any tool.
• Connecting Your Klaviyo Account: one-click Klaviyo connection, plus Omnisend and Mailchimp.
• Using Templates in Klaviyo: edit and send.

Figma to Klaviyo MCP: Frequently Asked Questions