Connect eBay to Store MCP
Checked against official docs on .
Connect an eBay seller in Stores, then verify identity before interpreting its catalog.
Platform summary
Supported work
- Read and edit supported listings
- Read and set inventory
- Read orders (read-only)
Not supported
- Fulfillment and tracking changes
- Refunds
- Cancellations
Writes need a paid plan, permission and provider support. Actual grants may be narrower.
Prerequisites
Use a seller account you control and a Store MCP account. Production Store MCP connects production eBay; sandbox acceptance is separate. Legacy Seller Hub inventory is not included simply because it appears in your seller dashboard.
Steps
- Sign in to Store MCP and open Stores. Choose eBay and start browser authorization.
- Check the eBay account shown on the provider consent page before accepting. Return to Store MCP and run the connection check.
- Connect your AI with View only access to that store. Ask for stores.list and stores.get, then confirm the seller and capability list.
- Read listings.list and one known Inventory API listing with listings.get. Read orders.list over a bounded period if orders exist.
Safe example
The example uses synthetic names. Select your own authorized store and verify every identifier before a write.
For my selected eBay seller, report its identity, capabilities and first page of Inventory API listings. Explain whether more pages exist. Do not publish, migrate or change anything.You’re done when…
Expect a healthy seller connection and either normalized results or a successful empty page. Compare with the same production/sandbox account. Empty production reads were live-tested; populated order mapping remains fixture evidence.
Limitations
Catalog and stock writes are supported with the required grants and paid entitlement. Fulfillment, tracking changes, refunds, cancellations and commerce events are disabled. Do not substitute a Trading API order ID for an opaque Store MCP order ID.
Sources and verification
Official documentation checked 2026-09-21. This is a documentation review, not a new live provider or client acceptance run.