In-depth architectural comparison of the Horoshop MCP and Tiny (Olist Tiny) MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Horoshop MCP
E-Commerce · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Tiny (Olist Tiny)
E-Commerce · Remote HTTP/SSE
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Horoshop MCP if you need specialized E-Commerce tools running via a local process. Choose Tiny (Olist Tiny) if your workspace requires E-Commerce integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Horoshop MCP when:
You need dedicated capabilities in the E-Commerce domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: HOROSHOP_STORES_FILE.
Primary tools included: 118 tools across API, storefront, and administration, Multi-store configuration through one server, Catalog, order, customer, and inventory operations.
Horoshop MCP is categorized under E-Commerce and uses a local stdio subprocess. In contrast, Tiny (Olist Tiny) belongs to E-Commerce using remote streaming HTTP/SSE transport. Select Horoshop MCP when you need capabilities focused on e-commerce and Tiny (Olist Tiny) when you require tools for e-commerce.