Skip to main content
Glama
developeron29

measuremy_site

by developeron29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to measuremy_site

No user-submitted related servers found.

    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
      11 npm
      MIT

    • OpenSEO-Lite

      Nagacash
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform live Google SERP searches, run on-page and full-site SEO audits with prioritized fixes, and check brand visibility in AI answer engines via four MCP tools.
      MIT

    • GrowthOS

      Astoriel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to answer growth questions in plain English by connecting to marketing and product data via 49 MCP tools.
      25
      MIT

    • Gizmo Analytics

      sudomichael
      A
      license
      A
      quality
      D
      maintenance
      Privacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.
      28
      85 npm
      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

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: the top_* family splits cleanly by dimension, and query_visits (aggregates) vs recent_visits (individual rows) are well separated. The only mildly fuzzy boundary is between get_whats_working and get_growth_actions, which both deal with marketing evidence/planning, though one analyzes and the other prescribes actions.

    Naming Consistency4/5

    Names use consistent snake_case and mostly follow verb_noun or prefix_noun patterns (get_overview, create_funnel, top_pages, delete_funnel). Minor deviations like recent_visits, find_traffic_spikes, and explain_spike break the strict pattern but remain readable and predictable.

    Tool Count4/5

    20 tools is on the heavy side but each covers a distinct analytics surface (traffic, sources, geo, tech, funnels, campaigns, spikes, annotations), so the set feels justified rather than padded. It sits at the upper edge of the ideal 3-15 range but is reasonable for a full-featured web analytics platform.

    Completeness4/5

    Coverage is broad: overview, timeseries, dimensional breakdowns, custom queries, raw recent visits, funnel create/get/delete, spike detection and explanation, annotations, tracked links, and campaign results. Minor gaps exist (no funnel update, limited event management), but core analytics and lifecycle workflows are covered with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources