list_reportsLABSCO SUMMARY
Campaign reporting without the dashboard.
The reports already exist in Kayzen; the friction is opening them. Here they are listed and fetched by id for whatever date range the question implies, and token refresh happens server-side so a long analysis session does not stall on re-authentication.
What it is
A TypeScript MCP server over the Kayzen Analytics API. It lists the reports on your account, fetches a report's results for a date range you name, and manages the auth token itself, refreshing it rather than making you re-authenticate.
What you get
- The reports available on your Kayzen account, each with its id, name and type
- One report's results fetched by id, with optional start and end dates written as YYYY-MM-DD, MM-DD, MM/DD, a month name or a month number; leave them out and the report's own date range is used
- Token management handled by the server, with automatic refresh
- A published npm package, @feedmob/kayzen-reporting, run through npx — the server now lives in FeedMob's fm-mcp-servers repository
Requirements
Node with npx, and your Kayzen username, password and basic auth token in the client config. The API base URL is optional and defaults to Kayzen's own.
Setup effort
Add the configuration to your client
USE CASES
01
Finding out what reporting you actually have
The report list comes back with id, name and type, so the next question can name the report instead of describing it.
02
Pulling a specific week of numbers
A report is fetched by id with a start and end date, and the data and metadata land in the conversation rather than as a download.
03
Keeping a long analysis session alive
The server refreshes the auth token as it goes, so a session that runs past the token lifetime keeps answering instead of failing halfway.
2 tools
Listed in project docs. Your client may show a different list.
get_report_resultsBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- Node.js
- npm
- KAYZEN_PASSWORD in your environment
- KAYZEN_BASIC_AUTH in your environment
- KAYZEN_USERNAME in your environment
INSTALLATION
Connect your client
MCP Clients
Claude Desktop — macOS
CLAUDE DESKTOP — MACOS · TERMINAL
curl -fsSL https://raw.githubusercontent.com/feed-mob/fm-mcp-servers/main/scripts/install.sh | bash -s -- kayzen-reportingClaude Desktop — npx
Open the Claude for Desktop configuration file (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json) and add:
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"kayzen": {
"command": "npx",
"args": [
"-y",
"@feedmob/kayzen-reporting"
],
"env": {
"KAYZEN_USERNAME": "user_email",
"KAYZEN_PASSWORD": "<YOUR_KAYZEN_PASSWORD>",
"KAYZEN_BASIC_AUTH": "baisc_auth_token"
}
}
}
}
