Skip to main content
Glama
A1-x-Tech

Google CrUX MCP

by A1-x-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Google CrUX MCP

No user-submitted related servers found.

    Related Servers

    • crux-mcp

      miguelrisero
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Chrome UX Report, providing real-user Core Web Vitals (LCP, INP, CLS) and historical trends for any origin or URL via natural language queries.
      3
      2
      MIT

    • chrome-ux-report

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying real-user Core Web Vitals field measurements — 75th-percentile LCP, INP, and CLS with distributions and ~40 weeks of history — for any origin or page that has enough Chrome traffic.
      416 npm
      MIT

    • Google Search Console MCP

      oscarcalvo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Google Search Console data, including search analytics with advanced filtering, quick wins detection, and rich dimensions, through natural language.
      5,260 npm
      MIT

    • Core Web Vitals MCP Server

      surendranb
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve real-user performance metrics and 28-day field trends, run Lighthouse lab audits, and access remediation playbooks for LCP, INP, and CLS.
      7
      157 PyPI
      MIT

    • seo-analytics-mcp

      zainsive
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Google Search Console, GA4, and IndexNow data via natural language, allowing users to ask about site rankings, clicks, indexing status, and conversions.
      13
      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

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: processed current assessment (get_core_web_vitals), device comparison (compare_form_factors), origin vs URL comparison (compare_origin_vs_url), historical trend (get_cwv_trend), and raw current/historical API queries (query_record, query_history_record). The processed/raw pairs are explicitly differentiated by use cases, leaving no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, with get_ for processed views, compare_ for comparisons, and query_ for raw API access. The naming clearly signals the action and domain, and while 'get_cwv_trend' uses an acronym, it remains consistent with the pattern.

    Tool Count5/5

    Six tools is a well-scoped count for a specialized CrUX server. Each tool fills a distinct niche—current, historical, comparisons, and raw access—without redundancy or bloat. The count is neither too thin nor excessive for the domain.

    Completeness5/5

    The tool set covers the core CrUX workflows comprehensively: single-point assessment, trend analysis, cross-device comparison, origin vs page comparison, and raw data access for custom analysis. There are no obvious dead ends or missing operations for the stated purpose of accessing CrUX data.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources