TimeLib MCP
Related Servers
Alternatives to TimeLib MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage Shopware e-commerce data through the Admin API, including products, categories, sales channels, orders, themes, and media.18 npm33MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read and write Shopify store data including products, orders, customers, inventory, and more via the Admin GraphQL API.2848 npmMIT
- AlicenseAqualityCmaintenanceExposes Shopify Admin API capabilities to LLMs, enabling product, order, customer, and inventory management via natural language.4937 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage Shopify store operations through the Admin GraphQL API, including products, orders, customers, inventory, and discounts via natural language, with safeguards for destructive actions and cost tracking.1637 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Shopify stores via natural language, with tools for products, orders, inventory, customers, and analytics.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceExposes Shopify Admin API as typed MCP tools for inventory, orders, revenue, and more, enabling Discord-based store management via AI agents.MIT
TDQS
Scored across 21 tools
Most tools have clearly distinct purposes (collections, categories, products, variants, inventory, orders, customers). However, create_collection/list_collections vs create_category/list_categories vs create_product/list_products all follow similar patterns and could be confused without careful reading, and the escaping medusa_admin_request overlaps with every curated tool's purpose.
The naming mostly follows verb_noun (create_collection, list_orders, get_product, update_variant, delete_variant, set_inventory_level). Minor deviations: get_store_context uses a non-verb + context noun pattern, and medusa_admin_request is a general escape hatch rather than a verb_noun operation. Otherwise consistent.
21 tools is on the heavy side but justified for a commerce backend covering products, variants, collections, categories, orders, customers, and inventory. The count pushes toward the upper boundary of reasonable scope, and the escape hatch tool adds useful flexibility but also breadth.
The curated surface covers core e-commerce lifecycle well: full CRUD for products/variants/collections, category and order/customer listing, and inventory management. Missing curated coverage for orders (no cancel/update status), customers (no create/update), and categories (no delete) is acknowledged and offloaded to the medusa_admin_request escape hatch, so agents have no dead ends.