Klaviyo MCP Server

Created By
relay-commercea year ago
Overview

What is Klaviyo MCP Server?

Klaviyo MCP Server is a comprehensive Model Context Protocol (MCP) server that provides complete access to Klaviyo's API functionality, enabling AI assistants to interact with Klaviyo APIs through 34+ tools covering profiles, campaigns, flows, lists, segments, events, and more.

How to use Klaviyo MCP Server?

To use the Klaviyo MCP Server, clone the repository, run the setup script, and configure your API key. You can then interact with the server using the MCP CLI or integrate it with AI assistants like Claude.

Key features of Klaviyo MCP Server?

  • Complete API coverage with 34 tools for major Klaviyo endpoints.
  • Secure authentication using Klaviyo private API keys.
  • Comprehensive error handling and rate limiting protection.
  • Consistent interface across all tools with JSON:API format support.
  • Detailed documentation with usage examples.

Use cases of Klaviyo MCP Server?

  1. Automating email marketing campaigns.
  2. Managing customer profiles and segments.
  3. Tracking customer events for analytics.
  4. Integrating Klaviyo functionalities into AI-powered workflows.

FAQ from Klaviyo MCP Server?

  • What programming language is used?

The server is implemented in Python 3.10 or higher.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • How can I contribute?

You can fork the repository, create a feature branch, and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
relay-commerce
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago