MCP use cases

Access: Settings → MCP

Complete jobs you can hand to your assistant with the Epinium MCP, from start to finish: what you need, how to ask for it and what to keep an eye on. Each one combines several MCP tools, which is exactly the kind of work that takes an afternoon by hand.

Copy your Amazon catalog to your Shopify or WooCommerce store

If you sell on Amazon and want to open or fill out your own store, your assistant can read your Amazon listings and use them to create the products in your Shopify or WooCommerce store: title, bullet points, description, images, brand and codes such as the SKU or the EAN. It works as a connector between the two accounts, with no files to export or import.

There is no button for this in the app: you ask the assistant in the conversation. If you want it to repeat on its own, for example every night with the new products, that is a workflow with store requests.

It is a copy, not a sync

The assistant copies what is on Amazon at the moment you ask. If you later change a listing on Amazon, your store does not find out: you will have to ask the assistant to update it, or set up a workflow that does.

What you need

• Both accounts connected in Settings → Connections: your Amazon account, Seller or Vendor, and your store.
• A key or an authorization with three permissions: Catalog to read your listings (catalog:read), Connections so it can find your store (connections:read) and Data from your connected stores and platforms on Edit to write to it (platform:read and platform:write). A key or an authorization you already had does not receive new permissions: create another one in Settings → API Keys or authorize the assistant again.
• A Business or Master plan. On Free and Guru the assistant can read both accounts, but cannot write to the store.
• Enough credits, as explained in How much it costs.

How to ask for it

1. Tell it which account, which marketplace and which store. Pick the marketplace whose language matches your store's: if your store is in German, copy from amazon.de.
2. Tell it what to copy and how. Content and codes carry over as they are. Price and stock belong to each channel, so tell it which price and which stock you want in the store: do not assume it copies Amazon's.
3. Start with one product. What the assistant writes to your store has no test mode. Ask it to create one, check it in your store and, if it looks the way you want, have it carry on with the rest.
4. Go in batches. By brand, by cluster or by a search, and a large catalog is better spread over several conversations.

A request that works well:

Copy the products of the Lumio brand from my Amazon Spain account to my WooCommerce store. For each one I want the title, the bullet points as the short description, the description, all the images, the brand, the SKU and the EAN. Set the price to Amazon's minus 10% and the stock to 0 for now. Before creating each product, check by SKU that it does not exist already. Start with just one and wait for me to review it.

Six things worth knowing

• It has to read the full listing. The Amazon product list only brings the basics: ASIN, SKU and title. Bullet points, description, images, brand, variations, price (on Seller) and stock come in parts of the listing the assistant has to ask for explicitly. If it tells you a listing has no description or images, ask it to read the full listing.
• Images travel by their address. The assistant passes the store the address of each Amazon image, and the store downloads and stores it.
• Duplicates are avoided by looking up the SKU. Before creating a product, the assistant looks it up in the store by its SKU. That is what lets you repeat the copy another day, or pick it up in another conversation, without creating the catalog twice. On top of that, every write carries a key that stops a retry from creating the same product again.
• Variations, in a second pass. An Amazon parent product with its children becomes a variable product with its variations in WooCommerce, or a product with options and variants in Shopify. It is the trickiest part: copy the products without variations first, review them and then move on to the ones that have them.
• WooCommerce, one product at a time. Each product, and each of its variations, is one call: Epinium does not allow batch creation. Each key has a limit of requests per minute, so a catalog of hundreds of products takes a while.
• Everything is recorded. Every product the assistant creates or changes stays in the store's change log for 12 months, with its result. Ask the assistant for it ("show me the latest changes in my store"). The log does not keep the previous value: if you are going to update products that already existed, have the assistant read them first.

How much it costs

• Reading your Amazon listings: 1 credit per product read. Reading the full listing costs nothing extra.
• Each read or write in your store: 5 credits plus 1 per KB of response, also when the store rejects the change because of invalid data. Looking up the SKU before creating is a read too.
• Minimum balance before each call to the store. Your balance has to cover the most that call could cost, about 2,050 credits at current rates, even if it ends up costing much less. If it falls short, the call is rejected before it reaches your store and at no cost.

What each resource costs is in Settings → Credits.