Klaviyo

Klaviyo MCP Pack — wraps the Klaviyo API for email marketing

Open source Repository Open in the app JSON README (API)

About

Klaviyo MCP Pack — wraps the Klaviyo API for email marketing

Details

Kind: MCP servers
Topic: Marketing & analytics
Publisher: pipeworx-io
Origin: official
Category: ferramentas
Transport: http
Version: 0.1.0
Last push: 2026-08-26T17:18:15Z
Repository state: ativo
Language: TypeScript
License: MIT
Added: 2026-08-29 04:01:08
Updated: 2026-08-29 04:01:08
Origin id: io.github.pipeworx-io/klaviyo

README

# mcp-klaviyo

Klaviyo MCP Pack — wraps the Klaviyo API for email marketing

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.

## Tools

| Tool | Description |
|------|-------------|
| `klaviyo_list_profiles` | Search contacts by email, name, or custom attributes. Returns profile IDs, emails, names, and properties with pagination support. |
| `klaviyo_get_profile` | Get a contact's full profile by ID. Returns email, name, phone, custom properties, list memberships, and subscription status. |
| `klaviyo_list_lists` | Get all email lists in your account. Returns list IDs, names, subscriber counts, and creation dates. |
| `klaviyo_list_campaigns` | Search campaigns by status (draft, scheduled, sent). Returns campaign IDs, names, status, send dates, and performance metrics. |
| `klaviyo_get_campaign` | Get a campaign's full details by ID. Returns name, status, subject line, recipient list, performance stats, and send history. |

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "klaviyo": {
      "url": "https://gateway.pipeworx.io/klaviyo/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/klaviyo/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Klaviyo data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT