Trendyol MCP
Related Servers
Alternatives to Trendyol MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Turkish e-commerce sellers to manage Trendyol marketplace store operations through AI assistants, including viewing products, orders, returns, and customer questions, with optional guarded write actions for answering questions and updating stock and prices.6MIT
- AlicenseAqualityBmaintenanceEnables LLMs to manage e-commerce seller workflows through natural language, including marketplace search, listing publication and updates, buyer questions, orders, shipping labels, messages, claims, reputation metrics, catalog, promotions, ads, and fulfillment operations. Provides 42 tools with OAuth authentication and a security layer.4219 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search, create, update, delete, and manage product listings, orders, shipping, questions, advertising campaigns, and more across 18 Latin American countries via the MercadoLibre REST API.203MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query and manage a MoySklad account through the JSON API 1.2 — reading stock, products, orders, counterparties and reports, and creating, posting or deleting documents — with a two-layer safety gate that keeps writes off until explicitly enabled and always drafts before posting.36MIT

3Dsellers MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage multichannel ecommerce operations, including product catalogs, listings, inventory, prices, orders, bulk edits, CSV imports, and buyer messages across eBay, Amazon, Walmart, Etsy, Shopify, and TikTok Shop. It connects through a hosted 3Dsellers account without requiring code or marketplace developer accounts.MIT- FlicenseNot gradedqualityDmaintenanceEnables eBay sellers to manage inventory, view orders, handle messages, and browse listings through AI assistants using eBay seller APIs.-
TDQS
Scored across 6 tools
Each tool targets a distinct stage of the workflow: search_docs/read_doc cover documentation browsing and reading, list_operations/get_operation cover API discovery versus detail, and list_stores/call_api handle store selection and execution. There is no meaningful overlap between any pair of tools.
All six tools use a single consistent convention: trendyol_ prefix plus a snake_case verb_noun pattern (search_docs, read_doc, list_operations, get_operation, list_stores, call_api). The verb choices are predictable and uniform across the set.
Six tools is well-scoped for a documentation-and-API-proxy server: four cover the docs/discovery lifecycle, one lists stores, and one executes any operation. No tool feels redundant and none is missing to the point of bloat.
The call_api generic executor plus docs/discovery tools give effectively full coverage of all Trendyol API operations, so no lifecycle dead ends exist for API calls. The only minor gap is that stores can be listed but not created or configured from within this tool set.