MarketplaceHub speaks the Model Context Protocol (MCP), so Claude or ChatGPT can read your account directly. Ask how many units of a SKU are left, which connection is failing, or whether last night's price push finished. The answer comes from your own data.
| SKU | eBay qty |
|---|---|
| LAMP-OAK-S | 2 |
| LAMP-ASH-M | 4 |
| SHADE-LIN-W | 0 |
It is the same data the REST API serves, through the same permissions and the same request allowance. Nothing new is exposed to an assistant that is not already yours.
Products and their listings, one SKU at a time or paged through the lot. Plus marketplace categories, the attributes each one requires and the values it accepts.
Which marketplaces are connected and the health of each, including the one that needs reconnecting. Which background imports, publishes or syncs are waiting, running or failed, and whether one really finished.
Name the SKUs and the new figures, and the change is pushed out to your connected marketplaces. Only if you granted the write permission for inventory.
Carrier, service and tracking number against the order items you name. The same confirmation the Orders queue sends, from a conversation.
Never twice. All six write tools are keyed. A repeat of the same call returns the first answer instead of doing the work again.
An assistant is new. The first things you hand one should not be the expensive ones.
Publishing writes to a marketplace against a schema that has to be exactly right. That is a poor first thing to hand an assistant, so it is not offered at all.
Money moves, and it does not move back on its own. Refunds stay with a person, in the Orders queue or through your own code on the API.
A buyer's name and address are left out of every order answer, unless the assistant asks for them on purpose. Most questions about an order do not need them.
Approving is what creates the access. Nothing happens before you do, and nothing is hidden afterwards.
In any client that supports a remote MCP server with OAuth, add https://api.marketplacehub.com/mcp as a custom connector. The assistant registers itself.
You finish on a normal MarketplaceHub sign-in page and see exactly what was asked for. That approval is the access.
Every call the assistant makes lands in your own request log, so you can see what it looked at and when.
After you sign in you are shown exactly what was asked for. An assistant can never be granted more than your account offers, and connecting one connects nothing else.
An assistant's calls appear in your request log next to your REST traffic. It draws on the same allowance, not a second one.
Every assistant you approved is listed in your account, with what it may do and who approved it. The list belongs to the account, so a colleague can disconnect one too.
The Agent Bot is built into the Merchant app, so there is nothing to connect.
Each answer uses 1 AI credit. A question that gets no answer costs nothing.
Press the Agent Bot row in the sidebar, or the robot button at the top of the screen on a phone. No setup, and no other assistant to connect.
It reads your products, orders, marketplaces, background jobs and AI credits, and links you to the right page for what it found.
Each team member sees only what their own role lets them see, by the same rule the pages themselves follow.
It can propose a price or stock change, a shipment confirmation, an AI re-run, or one missing value filled in on the listings that lack it. Nothing changes until you press Confirm on a card drawn from your own data, not from what the assistant says.
Which assistants, what they can reach, and how to stop one.
https://api.marketplacehub.com/mcp as a custom connector, the assistant registers itself, and you finish on a normal MarketplaceHub sign-in page. Older command-line tools may not support remote servers yet.Connect Amazon, eBay, Shopify and Etsy in one place.