Skip to main content
Glama
Sign In
Gizmo Analytics

Gizmo Analytics

by sudomichael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Gizmo Analytics

Related Servers

  • @lodd/mcp-server

    hholen
    A
    license
    A
    quality
    D
    maintenance
    First-party web analytics MCP server for AI agents, providing 42 tools to query traffic, events, funnels, conversions, sources, and performance data.
    40
    40 npm
    MIT

  • measuremy_site

    developeron29
    A
    license
    B
    quality
    B
    maintenance
    Cookieless web analytics your AI agent can read. Self-host it on your own Cloudflare account (Workers + D1) and read visits, sources, pages, countries and custom events over MCP. Prefer hosted? https://a.measuremy.site/mcp (OAuth sign-in, no key).
    20
    1
    MIT

  • lookout-mcp

    lookoutstats
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients such as Claude and Cursor to query Vercel Web Analytics across all your projects, covering visitors, sources, campaigns, Core Web Vitals, cross-site traffic, alerts and exportable board reports. It also supports annotations, resources and guided prompts for weekly briefs and traffic-drop investigations via a hosted or local server.
    82 npm
    MIT

  • fe

    runFleets
    A
    license
    Not graded
    quality
    D
    maintenance
    Multi-site analytics for AI agents — GA4, Google Search Console, Cloudflare edge, PageSpeed, and audit insights across all your websites as tools.
    20 npm
    MIT

  • Google Analytics MCP Server

    minholi
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to query Google Analytics 4 data—traffic, acquisition, top pages, audiences, events, conversions, and realtime metrics—through natural language. Supports local stdio use for a single user and HTTP multi-tenant OAuth for teams.
    1
    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

A3.9/5.0

Scored across 28 tools

Disambiguation4/5

Most tools have distinct purposes, with detailed 'ANSWER FIRST' cues. However, get_site_traffic overlaps with get_top_pages and get_top_referrers, and get_breakdown vs breakdown_by_property may cause confusion despite documentation distinguishing them.

Naming Consistency3/5

Naming uses snake_case and verb_noun pattern generally, but verbs vary inconsistently (e.g., 'get' vs 'list' for similar queries, and 'breakdown_by_property' vs 'get_breakdown'). Some names like 'identify_dead_sites' and 'detect_anomalies' have overlapping connotations.

Tool Count3/5

28 tools is on the high side for an analytics server. While each tool has a specific role, some could be consolidated (e.g., get_top_pages and get_top_referrers into get_site_traffic with parameters). The count is bordering on excessive but still justifiable.

Completeness3/5

Core analytics queries are well-covered, including traffic, breakdowns, funnels, goals, and anomalies. However, notable gaps exist: no delete_site or update_site, no remove_tag tool, and no update for goals/funnels. These missing operations could hinder full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo recent community issues

Resources