etsy-clean-mcp
Related Servers
Alternatives to etsy-clean-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables seamless integration with Etsy's marketplace API v3 to search listings, manage shop inventory, create and update products, optimize SEO, and access seller resources with OAuth support for authenticated operations.5-
- FlicenseBqualityCmaintenanceEnables Etsy sellers to manage their shops via natural language, including listing CRUD, bulk price and quantity updates by SKU, whole-shop A-F grade audits, photo uploads, shipping profiles, conversations, receipts, fulfillment tracking, and profit calculation.19-
- AlicenseNot gradedqualityCmaintenanceWraps the Etsy Open API v3 in pure capability primitives so AI agents can read and manage shops, listings, images, inventory, translations, digital files, receipts, payments, shipping profiles, taxonomy, reviews, users and buyer addresses, plus bulk listing and alt-text updates. It contains no baked-in scoring, SEO or tag-generation heuristics, leaving all judgment to the calling model.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Etsy sellers to manage their own shop's listings, orders, inventory, personalization, and media through AI assistants, scripts, or local applications using MCP tools, a CLI, and a local HTTP gateway.233 npm3MIT
- AlicenseBqualityDmaintenanceProvides full access to the Etsy Open API v3 for both buyer browsing and seller shop management through 37 specialized tools. It enables users to manage listings, process orders, handle shipping, and access inventory data via secure OAuth 2.0 authentication.4112MIT
- AlicenseAqualityCmaintenanceEnables interaction with the Etsy Open API v3, covering all 105 operations with authentication, scope management, and secure token refresh.724 npmMIT
TDQS
Scored across 16 tools
Each tool has a clear resource+action identity: read tools target distinct shop resources (shop, policies, profiles, sections, taxonomy, receipts, listings), and write tools split cleanly along listing lifecycle (create_draft_listing, update_listing, update_inventory, upload_listing_image, activate_listing) plus order fulfillment (add_tracking). The descriptions explicitly resolve the one plausible overlap by stating that price/quantity belong to update_inventory, not update_listing.
All 16 names follow a strict snake_case verb_noun pattern (get_*, list_*, create_*, update_*, upload_*, activate_*, add_*), with singular/plural nouns used correctly for single-resource vs collection operations. No camelCase or verb-style drift.
16 tools is at the upper edge for a shop-management server, but most earn their place given the breadth of the domain (listings, inventory, images, orders, taxonomy, shop config). A few read-only reference lookups (policies, sections, processing profiles, shipping profiles) could arguably be consolidated, but none are redundant with each other.
Listing creation/update/inventory/image/publish and order read+tracking are covered, but the lifecycle has a dead end: activate_listing exists with no deactivate or delete_listing counterpart, and images cannot be deleted or reordered. Reference data is read-only (policies, shipping/processing profiles, sections can only be listed, not created), which will block agents from fully setting up a shop.