Connect and Manage Multiple Stores

One MCP endpoint can expose several authorized stores without combining their identities or stock.

Prerequisites

Choose a plan with enough connected stores using Plans and usage. Authorize each seller account separately, even when two accounts use the same platform.

Steps

Connect the first store and record its Store MCP identity. Add the next available store through Stores.
Authorize the client for the intended subset in Connect AI; do not assume an existing grant includes a newly connected store.
List the visible stores and check each store’s capabilities. Read one known listing in each.
For a change, name exactly one store, listing and variant. Verify the result in that store before moving to another.

Safe example

The example uses synthetic names. Select your own authorized store and verify every identifier before a write.

Compare synthetic SKU DEMO-MUG in the two stores I select. Show store, listing, variant, location and quantity; flag uncertain matches. Do not synchronize or change stock.

You’re done when…

Expect separate store-attributed rows. Check each row against the provider dashboard. Similar names or SKUs alone do not establish that two records represent the same sellable unit.

Limitations

Multi-store access is not a staff/agency system. Reads are taken at different times and writes are not an atomic cross-platform transaction.

Compare inventory across channels

Explicitly match listings and variants by the merchant’s product knowledge. A canonical product can hold deliberate listing links; products.linkListing does not synchronize anything or automatically match SKUs. Read each inventory response independently.

Within one response, count one quantity per quantityPoolId, not every variation row. Pool IDs are not comparable across stores or between listing and inventory responses. Unknown quantities remain unknown. There is no shared stock pool or automatic replenishment.