Skip to main content
Glama
mcp-google-merchants

mcp-google-merchants

Related Servers

Alternatives to mcp-google-merchants

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Google Merchant Center through 34 tools across 9 modules, including account management, product operations, reports, inventory, promotions, shipping, return policies, collections, and recommendations.
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to manage Google Ads accounts by providing tools for querying account data and performing write operations such as updating campaign budgets, statuses, and bidding strategies.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Google Merchant Center, providing 126 tools to manage Google Shopping feed, products, inventory, reports, promotions, returns, and account configuration via natural language.
      813 PyPI
      19
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and modify a Google Ads account by running reports and creating or editing campaigns, budgets, ad groups, keywords, ads, and conversion actions, with validation-only and paused-by-default safeguards.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables management of Google Ads accounts via MCP, providing read and write tools for campaigns, ad groups, keywords, assets, and more, with support for reporting and mutations.
      -

    TDQS

    A4.1/5.0

    Scored across 28 tools

    Disambiguation4/5

    Almost every tool targets a distinct resource+action (accounts, products, product inputs, data sources, promotions, reports, auth flow), and descriptions explicitly cross-reference alternatives. The main soft spots are search_reports vs. the price_competitiveness/price_insights wrappers and vs. list_products filtering, which overlap in purpose though the docs explain when to use which. Auth helpers (start_login/finish_login/auth_status/setup_instructions) are a sequence, not duplicates, so they stay distinguishishable.

    Naming Consistency4/5

    Uniform snake_case throughout with a predictable verb_noun shape (list_accounts, get_product, insert_product_input, delete_product_input, create_data_source). A handful of tools drop the verb (auth_status, setup_instructions, price_competitiveness, price_insights, raw_request, logout), but they are still readable and stylistically consistent rather than chaotic.

    Tool Count3/5

    28 tools is on the heavy side of the rubric, driven largely by the six-step OAuth/onboarding flow plus a wide Google Merchant API surface. Each tool maps to a real API operation or documented convenience, so little feels padded, but the set is broader than an agent can comfortably hold in mind at once and could be consolidated (e.g. one auth tool, fewer report wrappers).

    Completeness4/5

    Covers the core lifecycle: account discovery, product-input CRUD, data-source create/list/fetch, promotion upsert/list/get, reporting, quotas and auth. Gaps are mostly deliberate (homepage claim and shipping-settings writes are read-only by design, no delete_data_source or promotion delete) and are explicitly routed to raw_request, so agents have a workaround. Inventory and returns sub-APIs are only reachable via the escape hatch.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues