Klaviyo MCP Server

Created By
mattcoatswortha year ago
Overview

what is Klaviyo MCP Server?

Klaviyo MCP Server is a comprehensive Model Context Protocol (MCP) server designed for interacting with the Klaviyo API, providing tools and resources for managing profiles, lists, segments, campaigns, flows, and more.

how to use Klaviyo MCP Server?

To use the Klaviyo MCP Server, clone the repository, install the dependencies, create a .env file with your Klaviyo API key, and start the server. You can also test the server using the MCP Inspector.

key features of Klaviyo MCP Server?

  • Complete coverage of Klaviyo API endpoints
  • MCP tools for all major Klaviyo operations
  • Easy integration with LLMs via the Model Context Protocol
  • Testing interface with MCP Inspector

use cases of Klaviyo MCP Server?

  1. Managing customer profiles and lists in Klaviyo.
  2. Automating email campaigns and flows.
  3. Analyzing metrics and events for marketing strategies.

FAQ from Klaviyo MCP Server?

  • What is the purpose of the Klaviyo MCP Server?

It serves as a bridge to interact with the Klaviyo API, simplifying the management of marketing data.

  • Is there a testing tool available?

Yes, the MCP Inspector allows you to test all available tools and resources.

  • What programming language is used?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

19 hours ago