Skip to main content
Glama
springwq

Kayzen Analytics MCP Server

by springwq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Kayzen Analytics MCP Server

No user-submitted related servers found.

    Related Servers

    • Google Ads MCP Server

      saikrishna406
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage, report, and analyze Google Ads campaigns securely with encrypted multi-client support, real-time API integrations, and audit trail logging.
      23 npm
      MIT
    • PaidSync MCP by PaidSync

      PaidSync MCPofficial

      PaidSync
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to create, manage, and optimize advertising campaigns across 14 ad and measurement platforms through a single MCP endpoint, with over 530 executable tools.
      3
      MIT

    • Google Ads MCP Server

      minholi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query campaign performance, metrics, audiences, and geography, and to analyze budgets, wasted spend, and account health through natural language.
      1
      MIT

    • Amazon Ads API MCP SDK

      NetzSicht
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI-powered advertising applications by providing MCP-compliant tools to interact with Amazon Ads API for campaign management, reporting, and optimization.
      3
      MIT
    • PaidSync MCP Server by PaidSync

      PaidSync MCP Serverofficial

      PaidSync
      A
      license
      Not graded
      quality
      F
      maintenance
      Connects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'get_report_results' appears to retrieve specific report data, while 'list_reports' enumerates available reports. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on whether it needs to list reports or fetch results from a particular report.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern ('get_report_results' and 'list_reports'), using snake_case throughout. The verbs 'get' and 'list' are standard and predictable, making the tool names easy to understand and use without confusion.

    Tool Count2/5

    With only two tools, the server feels under-scoped for an analytics domain, which typically involves operations like creating, updating, filtering, or deleting reports. This minimal set may force agents to work around gaps, such as being unable to generate new reports or modify existing ones, limiting functionality.

    Completeness2/5

    The tool surface is severely incomplete for analytics: it allows listing and retrieving reports but lacks essential operations like creating, updating, deleting, or filtering reports. This creates significant gaps that will likely cause agent failures when trying to perform common analytics tasks beyond basic read-only access.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources