Skip to main content
Glama
Sign In
flin-gmp-mcp

flin-gmp-mcp

by flin-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to flin-gmp-mcp

No user-submitted related servers found.

    Related Servers

    • Google Ads MCP

      zelentsov-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only inspection of Google Ads accounts through MCP, including account inventory, reporting, metadata, change history, and safe GAQL queries.
      Apache 2.0

    • Google Ads MCP Server

      RustamFaskhutdzinau
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Google Ads account data including campaigns, ad groups, keywords, and performance reports. Enables querying via GAQL through an MCP interface.
      MIT

    • flin-ga4-mcp

      flin-agency
      A
      license
      B
      quality
      B
      maintenance
      Enables read-only access to Google Analytics 4 properties through MCP tools for listing properties, inspecting metadata, checking metric compatibility, and running core or realtime reports, summaries, traffic-source, page, and event queries.
      17
      MIT

    • google-ads-mcp

      scalably-io
      A
      license
      A
      quality
      A
      maintenance
      Enables read-only access to Google Ads data through GAQL queries, resource exploration, recommendations, keyword planning and forecasts, and change history across manager and customer accounts.
      11
      23 PyPI
      MIT

    • ga-gsc-analytics

      horiiiiii032929
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Google Analytics 4 and Google Search Console data, allowing users to run reports, query search analytics, and generate combined snapshots for reporting.
      -

    • ga4-mcp

      goldvalleysolutions
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only access to Google Analytics 4 reporting data, including traffic overview, top pages, traffic sources, and conversion events, supporting custom report queries via MCP.
      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.3/5.0

    Scored across 32 tools

    Disambiguation4/5

    Tools are organized by product prefix (sa360/dv360/cm360) and each has a clear resource+action target, so most selections are unambiguous. A few pairs are subtle but are disambiguated by descriptions: list_dv360_reports vs list_dv360_report_queries vs get_dv360_report, and list_cm360_reports vs list_cm360_report_files vs get_cm360_report_file. list_sa360_customers vs get_sa360_customer_clients is also easy to mix up but the descriptions clarify the hierarchy distinction.

    Naming Consistency4/5

    Strong prevailing verb_noun pattern with a consistent product infix (list_dv360_campaigns, get_cm360_creative, create_dv360_report_query, read_dv360_report_rows). Minor deviations exist for single-target or non-resource actions: query_sa360, search_sa360_fields, authenticate, health_check. Overall predictable and readable.

    Tool Count3/5

    32 tools is heavy for a single server, though the scope genuinely spans three product families (SA360, DV360, CM360) plus auth/org discovery, so most tools earn their place. The report lifecycle alone consumes ~8 tools (queries, runs, status, rows, files) across two products, adding bulk. Borderline high rather than clearly bloated or clearly well-scoped.

    Completeness4/5

    The surface covers discovery, entity listing, and a fairly complete report lifecycle (create query, run, poll status, read rows) for DV360, plus generic read coverage of SA360 via query_sa360 and CM360 asset/report listing. Minor gaps: CM360 report execution/run tools are absent (only existing files can be listed), and SA360 has fewer dedicated read tools beyond the generic query. Intentional read-only posture is consistent and not a true dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources