Skip to main content
Glama
gioenjoy

mcp-google-merchant-center

by gioenjoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-google-merchant-center

No user-submitted related servers found.

    Related Servers

    • mcp-ga4

      mharnett
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language querying of Google Analytics 4, including reports, realtime data, custom dimensions, and property management.
      403 npm
      MIT

    • mcp-google-merchants

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to manage Google Merchant Center accounts via the Merchant API, including product feeds, promotions, data sources, and MCQL reports with read and write operations.
      28
      84 npm
      MIT

    • mcp-gads

      pijusz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and managing Google Ads campaigns, keywords, assets, and more via natural language, with support for multiple MCP clients.
      84 npm
      1
      MIT

    • Google Ads MCP

      danielpopamd
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing and analyzing ad accounts in plain language from AI assistants, including cross-account performance reports, keyword research, GAQL queries, and safe previewed changes.
      MIT

    • analytics-mcp

      rebecca-mcdonald
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Google Analytics data and configuration through natural language using the Data and Admin APIs.
      Apache 2.0
    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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clear, distinct aspect: account info, product details, product status, data sources, product listing, and product search. There is minimal overlap, as get_product and get_product_status differ in focus (details vs. approval), and list_products vs. search_products differ in scope (all vs. filtered).

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., get_account, list_data_sources). The verbs (get, list, search) clearly indicate the action, making the naming predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the server is well-scoped for querying a Google Merchant Center. The number is neither too few (covering essential read operations) nor too many (no unnecessary clutter). It fits the apparent purpose of data retrieval.

    Completeness4/5

    The tool set covers key read operations: account, product details, product status, data sources, and product listing/search. However, it lacks write operations (e.g., create, update, delete). This may be intentional for a query-only server, but for full lifecycle management, it's slightly incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources