mcp-google-merchants
Related Servers
Alternatives to mcp-google-merchants
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseAqualityDmaintenanceEnables reading products, checking approval statuses, and analyzing feeds across multiple Google Merchant Center accounts via natural language.615 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Merchant Center, providing 126 tools to manage Google Shopping feed, products, inventory, reports, promotions, returns, and account configuration via natural language.913 PyPI17MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseAqualityAmaintenanceEnables AI agents to read and write Google Analytics 4, Search Console, and Tag Manager data through MCP tools, with write operations gated behind an explicit flag for safety.2010 npmApache 2.0
TDQS
Scored across 28 tools
Each tool maps to a distinct resource and action: products, promotions, accounts, data sources, reports, quotas, and auth steps are cleanly separated. Even the two price wrappers and search_reports are clearly differentiated by their descriptions. raw_request is an explicit escape hatch rather than an ambiguous competitor.
The majority follow a consistent verb_noun pattern (list_products, get_promotion, insert_product_input, delete_product_input, create_data_source). The auth tools (start_login, finish_login, logout) and nouns like auth_status, setup_instructions, price_competitiveness, price_insights deviate but stay in snake_case and remain readable. No mixed casing or chaotic verbs.
At 28 tools, this sits above the typical 3-15 sweet spot and even above the 'heavy' 16-25 range, so the count is high. However, the server covers a very broad API surface (products, promotions, accounts, data sources, reports, quotas) plus a full auth setup flow, so nearly every tool has a distinct purpose. It is borderline bloated but not excessive.
The core product lifecycle is fully covered (insert/update/delete/get/list), and promotions have create/update, get, and list. Notable gaps are no dedicated delete_promotion, no data source update/delete, and read-only homepage/shipping settings, but raw_request covers those edge cases.