A
licenseC
qualityC
maintenanceA Model Context Protocol server enabling product searches across e-commerce platforms, price history tracking, and product specification-based searches using natural language prompts.
2
19
MIT
merch-connector
by grahamton
Related Servers
Alternatives to merch-connector
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA proof of concept MCP server that gives AI agents business context for e-commerce operations including orders, inventory, logistics, returns, claims, and payments.1-
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to search and compare products and generate Amazon affiliate purchase links.-
- AlicenseNot gradedqualityFmaintenanceMCP tool server that gives any AI agent the ability to search, scrape, and analyze content across the internet.42MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with a complete e-commerce application, providing authentication, product browsing, and shopping cart management through standardized MCP tools.-
- AlicenseAqualityDmaintenanceMCP server for the Cart e-commerce intelligence API, enabling AI agents to search stores, products, ads, and suppliers, and analyze market trends.157 npmMIT
TDQS
A4.2/5.0
Scored across 14 tools
Disambiguation4/5
Most tools have clear, distinct purposes with explicit guidance (e.g., acquire is the primary entry point, scrape_pdp is for PDPs, scrape_page is deprecated). However, some analytical tools (merch_roundtable, analyze_products, ask_page) have overlapping functionality, though descriptions clarify input sources.
Naming Consistency4/5
Tool names generally follow a verb_noun snake_case pattern (scrape_pdp, compare_storefronts, list_evals). A few exceptions like 'acquire', 'site_memory', and 'merch_roundtable' deviate slightly, but the overall pattern remains consistent and readable.
Tool Count5/5
With 14 tools, the server is well-scoped for its purpose, covering scraping, analysis, interaction, comparison, memory, and evaluation. Each tool earns its place, and the count is within the optimal range.
Completeness4/5
The server covers the full workflow: acquire data, scrape specific products, interact, compare, ask questions, analyze offline, and save/list evals. Minor gaps include no explicit delete for evals or memory, but these are not critical to the core functionality.
Maintenance
ActivityInactive
ResponsivenessNo issues