medusa-mcp
Related Servers
Alternatives to medusa-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server exposing WIBI's API v2 as tools, supporting OAuth 2.1 for production (Claude web/desktop) and stdio for local dev, enabling natural-language queries about campaigns, products, clients, reports, broadcasts, and subscriptions with per-commerce isolation and admin scope switching.-
- FlicenseNot gradedqualityCmaintenanceProvides a production-oriented MCP server exposing tools, resources, and prompts over Streamable HTTP with JWT authentication and per-tool RBAC, enabling Amazon Bedrock Claude clients to securely invoke MCP capabilities.-
- AlicenseBqualityDmaintenanceA minimal local MCP server that wraps any Claude Messages API-compatible upstream into a unified ask_model tool. It enables MCP clients to interact with these models through a standard tool interface using stdio transport.18MIT
- AlicenseAqualityDmaintenanceStart, observe, and interact with Claude Managed Agents from any MCP client — launch an agent, watch its events, reply, approve the tools it wants to run, and stop it. Runs over stdio, HTTP, or AWS Lambda with pluggable auth.171MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that connects Claude to Shopify stores, enabling natural language queries and actions on products, orders, customers, inventory, and sales analytics. Includes a demo mode with bundled fixtures for trying tools without credentials.97 npmMIT
- AlicenseNot gradedqualityDmaintenanceTurns any CLI tool or REST API into an MCP server for Claude, enabling Claude to use git, databases, or any API through natural language.MIT
TDQS
Scored across 17 tools
Each tool targets a distinct resource and action: list/get pairs for orders, customers, products and inventory; mutating tools like set_stock_level, complete_order, cancel_order, create_fulfillment and create_shipment are clearly separated. There is no meaningful overlap that would cause an agent to misselect between tools.
The set uses a consistent snake_case verb_noun pattern for the vast majority of tools (list_orders, get_order, set_stock_level, complete_order, create_fulfillment, cancel_order, update_product, delete_product, set_variant_price). The only notable deviation is sales_report, which is a noun phrase rather than a verb_noun, but overall the convention is predictable.
17 tools is slightly on the heavy side but appropriate for an e-commerce admin surface spanning orders, customers, products, inventory, fulfillments and reporting. Each tool appears to earn its place, though the set could be tightened marginally.
The surface covers reads and several lifecycle actions well but has notable gaps: there is no create_product despite update/delete, no create_customer or update/delete_customer, and no order creation. These are common admin operations that an agent may reasonably expect, causing dead ends in otherwise well-covered domains.