Melbis Shop
OfficialRelated Servers
Alternatives to Melbis Shop
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceOfficial MCP server for NanoCart, enabling AI agents to manage products, orders, coupons, categories, subscribers, settings, and pull sales reports from your store.3166 npmMIT
- FlicenseBqualityDmaintenanceAn unofficial MCP server that connects AI agents to Horoshop e-commerce stores, providing tools for managing orders, products, and store operations via the Horoshop API.71-
- FlicenseNot gradedqualityBmaintenanceMCP server for the OffByOne website factory, enabling agents to generate, validate, and manage full-stack web projects through safe, deterministic tools.-

MoltJobs MCP Serverofficial
AlicenseBqualityCmaintenanceOfficial MCP server for MoltJobs, enabling AI agents to browse and bid on jobs, execute work, submit results, and manage USDC wallets on the marketplace.3732 npmMIT- AlicenseNot gradedqualityBmaintenanceAn MCP server for e-commerce storefronts that lets AI agents search and browse products, get quotes, and access back-office data (like sales and orders) with privilege separation, using public and authenticated tools.49 npm1Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for the operbots panel, enabling AI assistants to manage tasks, Telegram bots, flow scenarios, conversations, knowledge base, and AI connections with the user's permissions.82357 npmMIT
TDQS
Scored across 56 tools
Every tool is namespaced by resource (html, static, image, php, db, memory, tool, shop, session) and action, so even similar operations are clearly distinguishable. Ambiguous pairs like tool_run vs shop_run are explicitly contrasted in their descriptions.
Most tools follow a predictable snake_case resource_action pattern, with consistent add/load/save/rename/remove verbs within each file type. A few names like engine_whole_load, engine_map_tree, engine_db_tables, and engine_search break the pattern but remain readable.
56 tools is a very large surface, far beyond the 16-25 'heavy' range, even for a broad shop-administration scope. The count will burden agent tool selection and could benefit from consolidation or grouping.
The set provides thorough CRUD/lifecycle coverage for templates, statics, images, PHP files, database operations, memory, custom tools, and shop access. Minor gaps remain: config is read-only, there is no session disconnect, and element files lack rename/update operations.