Klaviyo API MCP Server

If you already use Klaviyo API, the klaviyo api mcp server is the piece that lets your assistant work with it directly. # Klaviyo API MCP Server A comprehensive Model Context Protocol (MCP) server for interacting with Klaviyo's API. This server provides tools and resources for managing profiles, lists, events, campaigns, flows, templates, segments, metrics.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• get_profiles — Get a list of profiles with optional filtering
• get_profile — Get a specific profile by ID
• create_profile — Create a new profile
• update_profile — Update an existing profile
• delete_profile — Delete a profile
• get_lists — Get all lists
• get_list — Get a specific list by ID
• create_list — Create a new list
• update_list — Update an existing list
• delete_list — Delete a list
• get_list_profiles — Get profiles in a list
• add_profiles_to_list — Add profiles to a list

Credentials and setup notes

Configuration is passed through the environment: KLAVIYO_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Klaviyo API's toolset — get_profiles, get_profile, create_profile and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mattcoatsworth; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Klaviyo API.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.