Kayzen MCP Server

If you want an AI assistant working directly with Kayzen MCP, the kayzen mcp mcp server is the bridge. Kayzen Analytics MCP Server for Claude Desktop.

What Kayzen MCP does

A Model Context Protocol (MCP) server implementation for interacting with Kayzen Analytics API. This package enables AI models to access and analyze Kayzen advertising campaign data through a standardized interface.

Key capabilities

• Automated Authentication — Built-in token management with automatic refresh mechanism
• Report Management — Easy access to Kayzen analytics reports
• Error Handling — Comprehensive error handling for API interactions
• TypeScript Support — Full TypeScript implementation with type definitions
• Environment Based Configuration — Simple setup using environment variables

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

• Prerequisites — The Prerequisites tool exposed by this server
• Scripts — The Scripts tool exposed by this server

Installing the kayzen mcp mcp server

The server is distributed via npm as @feedmob-ai/kayzen-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 4 environment variables: KAYZEN_USERNAME, KAYZEN_PASSWORD, KAYZEN_BASIC_AUTH, KAYZEN_BASE_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js (v16 or higher) - npm (v7 or higher) - Kayzen API credentials

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Kayzen MCP sits in that group, and the shape of its toolset — Prerequisites, Scripts — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by springwq, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the kayzen mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.