A REST API over the same data your dashboard runs on — orders, products, inventory, marketplaces and jobs — plus webhooks so your own systems hear about a change the moment it happens, instead of polling for one. The same account is reachable over MCP, so an AI assistant can read it without you writing a client at all.
The API reads and writes the same catalogue your dashboard does, scoped to your own account — never a marketplace's API on your behalf, and never your marketplace credentials.
List every marketplace order in one feed, then confirm shipment with carrier and tracking, cancel, refund a line, or update one — the same actions the dashboard queue gives a merchant.
Create a product, read one back, search product types by marketplace category and push a price-and-quantity update — enough to drive your catalogue from an ERP or warehouse system instead of a spreadsheet.
List the marketplaces connected to your account and check the status of a background job — an import, a publish, a sync — without leaving your own tooling.
Register an endpoint once and get pushed the events you care about as they happen, instead of polling the API on a schedule to find out what changed.
Generate a key from your account settings. It only ever reaches your own account's data — there's nothing to scope down.
Every endpoint, request shape and response is documented in the reference, with a live Swagger UI to try a call before you write any code.
Register an endpoint for the events you need, and stop polling — see the webhooks reference for the full event list.
The same account, the same permissions and the same request allowance — reached by an AI assistant over the Model Context Protocol instead of by code you wrote. Nothing new is exposed.
https://api.marketplacehub.com/mcp, added as a custom connector. The client
registers itself, so there is no credential to mint for it and no secret to paste back.
The merchant signs in and approves a named scope set. A client can never be granted more than the account offers, and approval is per client rather than per account.
Nine read — products, product types, marketplaces, jobs and orders. Two write: set price and stock, and confirm a shipment. Each costs the scope its REST twin costs.
A tool call is metered against the same per-endpoint allowance as the REST route behind it and appears in the same request log — speaking MCP does not buy a second allowance.
What the API covers today, how it's secured, and where to find the full reference.
https://api.marketplacehub.com/mcp; it registers itself and sends the merchant to a normal sign-in and consent screen, so there is no API key in the loop. Nine tools read and two write. You need it only if an assistant is the consumer — for code you write, the REST API is the same data. See the MCP reference.Warnings entry naming the platform, so read Warnings on every write.No questions in this category.
Connect Amazon, eBay, Shopify and Etsy in minutes. Centralize inventory, automate listings, and let AI handle the busywork — so you can focus on selling more.
Shopify
5 active
Etsy
3 active