Klaviyo
Server Details
Klaviyo MCP Pack — wraps the Klaviyo API for email marketing
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-klaviyo
- GitHub Stars
- 0
- Server Listing
- Klaviyo MCP Server
TDQS
Scored across 36 tools
Massive overlap among tool purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are three near-identical universal routers, and deep_research, entity_profile, recent_changes, compare_entities, and resolve_entity all answer overlapping 'tell me about X' style requests. The Klaviyo-named server also contains dozens of unrelated Pipeworx tools, so an agent cannot infer scope from the name.
Names are mostly snake_case, but the set mixes several conventions: a klaviyo_ namespace prefix, a pipeworx_ prefix, pipeworx-suffixed variants (ask_pipeworx, _beta, _grounded), and bare single-word tools (remember, recall, forget, subscribe, unsubscribe). Readable but not a single predictable verb_noun pattern.
36 tools is well beyond the reasonable band for a domain-scoped server, and dramatically mismatched for something called 'Klaviyo' (which only has 5 actual Klaviyo tools). Most of the surface is generic gateway/meta functionality that doesn't earn its place under this server's identity.
If the domain is Klaviyo, coverage is severely incomplete: only list/get for campaigns, profiles, and lists — no create/send/update/delete, no segments, flows, or metrics. If the domain is the Pipeworx gateway, the bundled surface is broad but the server identity is broken, leaving obvious dead ends for the stated purpose.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Mailchimp MCP Pack — manage audiences, campaigns, and members via Mailchimp Marketing API.
ActiveCampaign MCP Pack — email marketing + CRM (API v3).
Close CRM MCP Pack — wraps the Close (close.com) API v1.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Klaviyo API for marketing automation, including managing lists, campaigns, and customer data.1MIT
- FlicenseDqualityDmaintenanceA comprehensive MCP server for interacting with the Klaviyo API, providing tools and resources for managing profiles, lists, segments, campaigns, flows, and more.416-
- FlicenseDqualityDmaintenanceProvides comprehensive tools and resources for managing Klaviyo marketing automation, including profiles, lists, campaigns, flows, and more through natural language.483-
- FlicenseNot gradedqualityDmaintenanceEnables Claude to access Klaviyo campaign and flow reporting, including email and SMS performance metrics, via MCP stdio or a Flask REST API.-
Glama MCP Gateway
Add one secure layer between your agents and this server.