Skip to main content
Glama
azuostech

MCP Marketing Analytics

Official
by azuostech

Related Servers

Alternatives to MCP Marketing Analytics

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server that provides tools and resources for interacting with Google Ads API, enabling search, metadata retrieval, and account management through natural language.
      3
      2,477 PyPI
      963
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Python MCP server that exposes Meta Marketing API data, providing tools to manage ad accounts, campaigns, and analytics through natural language interfaces.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that exposes the Google Ads API to LLM clients, enabling account inspection, GAQL queries, performance reporting, and campaign management.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Google Ads campaign reporting and management via Claude, enabling GAQL queries, performance metrics, and campaign modifications.
      20 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Google Ads API that enables LLMs to search and query Google Ads accounts, retrieve resource metadata, and generate keyword ideas.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing Google Ads campaigns through the official Google Ads API, covering accounts, campaigns, budgets, keywords, search terms, and keyword ideas. It provides tools for both reading and mutating live ads data, such as pausing campaigns, updating budgets, and adding keywords.
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct step in the analytics workflow: source discovery, account discovery, field discovery, query execution, and result retrieval. There is no overlap between these purposes, so an agent can confidently select the right tool.

    Naming Consistency3/5

    The first three tools follow a consistent 'X_discovery' pattern, but the last two deviate with 'data_query' and 'get_query_results', mixing structural conventions. While all names use snake_case, the inconsistency in pattern makes the naming less predictable.

    Tool Count5/5

    With only five tools, the set is well-scoped for a focused marketing analytics server. Each tool serves a necessary function in the pipeline without redundancy or bloat.

    Completeness5/5

    The tool set covers the full discovery-to-results lifecycle: discover sources, accounts, fields, execute a query, and retrieve results. There are no obvious gaps for read-only analytics operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues