1. Conduid
  2. Developer Tools
  3. Klaviyo
MCP server · Developer Tools

Klaviyo

by · github.com/universal-mcp/klaviyo

Klaviyo MCP Pack — wraps the Klaviyo API for email marketing

Unclaimed last commit 8 months ago comms
InstallView source
37Low

Scored yesterday · breakdown

About Klaviyo

Klaviyo is an MCP server published by universal-mcp in the Developer Tools category: klaviyo MCP Pack — wraps the Klaviyo API for email marketing.

The repository has 1 stars and 0 forks, with the last commit 8 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

Claude Code
claude mcp add klaviyo -- npx -y klaviyo-mcp
npx
npx -y klaviyo-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Klaviyo

Powered by Claude · Grounded in docs

I know everything about Klaviyo. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository just now. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • ✓Tests presentA test suite exists in the repository.
  • !Dependencies pinnedNo lockfile. Installs can pull different code over time.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.1.1v0.1.1

README

Welcome to the Universal MCP Klaviyo API. This project provides a starting point for your API application, generated automatically by MCP CLI to help you kickstart your development quickly.

📋 Prerequisites

Before you begin, ensure you have met the following requirements:

  • Python 3.11+ (Recommended)
  • uv installed globally (pip install uv)

🛠️ Setup Instructions

Follow these steps to get the development environment up and running:

1. Sync Project Dependencies

Navigate to the project root directory (where pyproject.toml is located).

uv sync

This command uses uv to install all dependencies listed in pyproject.toml into a virtual environment (.venv) located in the project root.

2. Activate the Virtual Environment

Activating the virtual environment ensures that you are using the project's specific dependencies and Python interpreter.

  • On Linux/macOS:
source .venv/bin/activate
  • On Windows:
.venv\\Scripts\\activate

3. Start the MCP Inspector

Use the MCP CLI to start the application in development mode.

mcp dev src/universal_mcp_klaviyo/mcp.py

The MCP inspector should now be running. Check the console output for the exact address and port.

🚀 Usage

Once the server is running, you can test the tools and interact with them.

📁 Project Structure

The generated project has a standard layout:

.
├── src/                  # Source code directory
│   └── universal_mcp_klaviyo/
│       ├── __init__.py
│       └──   mcp.py      # Server is launched here
│       └──   app.py      # Application tools are defined here
├── tests/                # Directory for project tests
├── .env                  # Environment variables (for local development)
├── pyproject.toml        # Project dependencies managed by uv
├── README.md             # This file

➡️ Next Steps

📄 License

This project was generated using MCP CLI — Happy coding! 🚀

README fetched from the repository just now. The original is authoritative.

Questions

About Klaviyo

How do I install Klaviyo?

Run claude mcp add klaviyo -- npx -y klaviyo-mcp, then add the server to your MCP client's configuration.

Is Klaviyo safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 3 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Klaviyo still maintained?

The last commit was 8 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.