Klaviyo MCP Server
Related Servers
Alternatives to Klaviyo MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseDqualityDmaintenanceA comprehensive Model Context Protocol server that enables interaction with the Klaviyo API, providing tools and resources for managing customer profiles, lists, segments, campaigns, flows, and various marketing automation features.473-
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server for the Mautic marketing automation API, providing 203 tools for managing contacts, campaigns, emails, segments, and more.2-
- AlicenseAqualityCmaintenanceMCP server for Keap CRM, providing tools to manage contacts, tags, opportunities, notes, tasks, campaigns, and users via the Keap REST API v1.15Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for interacting with Keap CRM, enabling contact and tag management, batch operations, custom fields, and advanced query optimization.MIT
- AlicenseAqualityBmaintenanceMCP server for the Influencers Club API — creator enrichment, discovery, audience analysis, content data, batch operations, and account management.222,626 PyPI4MIT
- FlicenseCqualityDmaintenanceComprehensive MCP server for Mailchimp Marketing API v3.0 with over 104 tools and 15+ React UI apps, enabling management of campaigns, audiences, ecommerce, automations, reports, and more via natural language.1001-
TDQS
Scored across 41 tools
Many tools follow a plural/singular pattern for list vs single resource, which helps distinguish them. However, tools like delete_profile and request_profile_deletion appear to overlap, and pairs like get_metric/get_metrics rely on naming convention alone without descriptions, creating potential misselection.
Most tools use a consistent verb_noun pattern (get, create, update, delete, add), and plural/singular nouns generally indicate list vs single. Inconsistencies exist, such as add_profiles_to_list (plural) vs add_tag_to_resource (singular), and request_profile_deletion deviates from the delete_* style.
With 41 tools, the server is well above the typical 3-15 range. Many resources have both plural and singular getters, inflating the count, and the broad scope makes it feel heavy rather than well-scoped.
The server provides extensive read operations but lacks update/delete for many resources (lists, segments, templates, catalogs, etc.), no remove_tag_from_resource, and no update operations for webhooks or coupons. This leaves significant lifecycle gaps for a CRUD-style API.