Loja Aurora
Related Servers
Alternatives to Loja Aurora
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables safe, read-only analysis of e-commerce data, including semantic product search, sales summaries, top products, customer orders, and low-stock alerts, through MCP tools and a LangGraph agent.5MIT
- FlicenseNot gradedqualityDmaintenanceEnables e-commerce shop owners to query their business data using natural language through local AI models. Provides secure, privacy-focused access to sales reports, inventory management, customer analytics, and order data without sending sensitive information to external services.-
- AlicenseAqualityBmaintenanceGives LLM agents structured access to e-commerce products, inventory, orders and sales analytics through eight MCP tools, backed by durable local SQLite state that survives restarts. It runs zero-config on a bundled mock dataset, with a swappable data-provider seam for live Shopify/Stripe connections.8MIT
- FlicenseAqualityDmaintenanceEnables AI agents to answer analytical questions about an online store's SQLite database through specialized read-only tools, without any risk of modifying the underlying data.8-
- AlicenseAqualityDmaintenanceEnables AI agents to safely interact with a SQLite shop database through schema discovery, read-only SQL queries, and pre-built analytics reports like top customers, top products, and revenue summaries.667 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude, ChatGPT, Cursor, or any MCP client to a Shopify store, enabling read-only access to themes, Liquid files, catalogue data, and store configuration through 122 tools.2Apache 2.0
TDQS
Scored across 8 tools
Each tool targets a distinct resource: customer lookup, orders per customer, order detail by number, sales aggregates, top products, policy text, plus a schema and SQL pair. The only fuzziness is between customer_orders/get_order and sales_summary/run_sql, but descriptions make the intended precedence clear (run_sql is explicitly a last resort).
All names are snake_case and readable, but the conventions are mixed: verb_noun (find_customer, get_order, search_policies, run_sql, describe_schema) alongside noun-first/aggregate names (customer_orders, sales_summary, top_products). Predictable enough to use, but not a single consistent pattern.
Eight tools is well-scoped for a small store analytics/assistant domain. Each tool earns its place, and the run_sql/describe_schema pair is a sensible controlled escape hatch rather than padding.
Covers the main read paths: customer lookup, order history, order detail, period sales, top products, and policy search, plus SQL fallback for anything else. Minor gaps exist for product catalog/stock lookup and structured return or exchange records, but the SQL escape hatch lets agents work around most of them.