Klaviyo API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KLAVIYO_API_KEY | Yes | Your Klaviyo private API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 48 tools
With 48 tools and no descriptions, agents must rely solely on tool names. While names like create_campaign and get_campaigns are clear, similar names (e.g., get_catalog vs get_catalogs, get_metric_aggregate vs get_metric_timeline) create ambiguity without explanatory context.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_campaign, delete_profile, get_metrics). There are minor deviations like remove_profiles_from_list, but the overall pattern is uniform and predictable.
48 tools is excessive for most MCP servers. Even for a comprehensive API like Klaviyo, this many tools make the surface unwieldy and increase cognitive load, exceeding the recommended upper bound of 25.
The tool set covers CRUD operations for major resources (campaigns, lists, profiles, templates, catalog items) and includes specialized actions (send_campaign, clone_template, add_profiles_to_list). Minor gaps like missing delete operations for events and flows prevent a perfect score.