A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
3 ★ · melbis/melbis-shop · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 3 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository melbis/melbis-shop;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals
🛒 Melbis Shop — self-hosted e-commerce with an AI agent on staff
**Melbis Shop** is a self-hosted e-commerce platform: your server, your domain, your data. A native **Windows back-office** and a **PHP storefront** share one business logic, and the package ships an **MCP server**, so an AI agent — Claude Code, Goose, Cherry Studio, anything that speaks MCP — works in your store as an employee: under a staff login, with that person's permissions, every action signed by their name. Built since 2002 for stores with real teams: several suppliers and price lists, hundreds to hundreds of thousands of products, staff who must not see each other's data. --- 🎯 Who it is for A seller who has outgrown a marketplace and wants an own channel next to it — with a team of two to five people, suppliers' price lists and hundreds of SKUs. Not a page builder for a single product. ⚙️ Installation is automatic You do not touch a console. In the Windows client you enter three things — the server's address, its root password and your domain — and the client installs everything over SSH itself: Docker, nginx, MySQL, PHP, the SSL certificate, the store. Updates run the same way, from the same window. A clean Ubuntu VPS becomes a working store in one sitting. Seven steps with screenshots, from renting a server to the first task for the agent: https://melbis.com/en/doc/install/start/ 🤖 What the AI agent does here - **56 MCP tools** in the box: project files (modules, templates, statics, images — with version history), the database (pools of steps with locks and cache marks), catalogue trees, product files, storefront pages as a visitor sees them, and the platform documentation itself. - **26 store tools with 244 commands** come with the demo store: products and prices, descriptions, catalogue and attributes, suppliers, orders, scheduler tasks, users, image profiles, batch import of goods and files. - **Permissions per command.** Tools are data, not code: the owner grants each command to a person or a group. An employee with no database access still runs the agent — inside their own rights. - **A real run, with the log and screenshots:** one message in plain words → the first working version of a store — currencies, suppliers, a catalogue with 12 products, three roles with separate rights, a business-process roadmap — in **24 min 45 s and 21.2k tokens**. Half an hour more: a redesign from a free third-party template. → https://melbis.com/en/doc/install/ai_work/ Connecting an MCP client The MCP server (MelbisMCP.exe, stdio) is installed together with the Windows client — nothing to download separately. In the client open *System → Connection → AI Assistant*: the ready configuration is there with a **Copy** button for Goose, Cherry Studio and other MCP applications; **Check Connection** tests the licence, the login and the rights and says in words what is missing. Claude Code needs no configuration at all — the client writes .mcp.json into the store folder, open that folder as a project. The agent signs in under the person who runs it; there is no separate AI account, licence or password in the chat. 🚀 What makes the platform different - 🧮 **One business logic** for the storefront and the back-office: an order is calculated by the same code in the Windows app and on the site. Nothing to synchronise, nothing to diverge.