eBay

You only need the seller's eBay login and permission to approve ShopMCP. Sellers do not need to create an eBay Developer account or paste app credentials into ShopMCP.

• Use a real seller account for production data. Sandbox accounts only show sandbox listings and orders.
• For listing creation through eBay's Inventory API, the seller should have payment, fulfillment, and return business policies available.
• Agencies should connect each seller account separately and label the account after OAuth completes.

Open Settings - Integrations, choose eBay, then start the consent flow for the seller's primary marketplace.

ShopMCP sends eBay's marketplace header for the selected account. Some tools also accept a marketplace override when eBay supports that safely.

eBay shows a permission screen for the seller account. After approval, eBay redirects through ShopMCP's eBay app RuName, ShopMCP exchanges the authorization code, checks the seller identity, and stores the refresh token encrypted at rest.

• Read access covers listings, categories, aspects, policies, inventory, offers, orders, payouts, ads, analytics, stores, messages, feedback, and feed tasks.
• Write permissions are requested up front so sellers do not need to reconnect later, but write tools stay hidden until writes are explicitly enabled.
• ShopMCP stores the seller id, marketplace default, granted scopes, token expiry, and encrypted OAuth tokens on the connection.

• Find active eBay listings missing required category aspects or recommended item specifics.
• Compare eBay listing price, stock, and traffic against Shopify or Neto product data.
• Check eBay orders, fulfillments, disputes, refunds, finance transactions, payouts, and seller funds.
• Review Promoted Listings eligibility, campaigns, ads, keywords, reports, and seller-offer opportunities.
• Monitor seller standards, customer service metrics, store categories, conversations, feedback, and feed tasks.

eBay has two important listing models. ShopMCP keeps them separate so the AI client does not edit the wrong surface.

Inventory API listings

New SKU-based listing workflows use eBay's Inventory API: inventory item, location, offer, business policies, then publish. Inventory API-managed listings should be revised through Inventory API tools.

Legacy active listings

Many sellers already have active listings created in Seller Hub, old third-party tools, or eBay's Trading API. These may not appear in Inventory API inventory queries. ShopMCP uses a separate Trading API bridge to read or revise those listings, or can migrate eligible fixed-price listings when the seller explicitly wants Inventory API management.

Write tools only appear when the workspace Allow writes toggle is enabled and the global integration writes mode allows it. When enabled, writes can change buyer-visible listings, inventory, order fulfillment, refunds, messages, feedback, promotions, and ad spend.

• Confirm seller account, marketplace, listing/order/campaign id, and exact field changes before any write.
• Do not bulk-write in loops unless the full itemized batch has been approved.
• Use sandbox first when testing listing creation, refunds, messaging, feedback, or advertising workflows.

ShopMCP's connection flow follows eBay's official OAuth authorization-code and RuName model. eBay's Inventory API docs also note that Inventory API listing flows need business policies, and eBay's marketplace metadata uses the marketplace IDs shown above.

• eBay authorization and RuName guide
• eBay Inventory API overview
• eBay business policies
• eBay supported marketplace IDs