Connect eBay to Claude Code

Let Claude revise listings and answer buyers in eBay. From the terminal, inside the sessions where you already work.

How do you connect eBay to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect eBay, you add a eBay MCP server: a small hosted service that exposes eBay's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own eBay account. No API keys pasted into config files.

claude mcp add --transport http ebay https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in eBay once connected?

Full read-write eBay access lets Claude revise an active listing's price or title, update stock for a variation, answer a buyer's question, send an offer to a watcher, and prepare a refund once you approve. The listing edits and buyer replies that used to mean tabbing through Seller Hub happen in one place.

Revise an active listing's price, title, or item specifics
Update inventory quantity for a SKU or variation
Reply to a buyer's message or pre-sale question
Send a Best Offer or offer to watchers on a listing
Prepare a return or refund for your approval before it is issued
Mark an order shipped and add tracking once you confirm

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same eBay access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the eBay API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when eBay changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build eBay connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same eBay connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own eBay account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on eBay's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to eBay?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the eBay account it signs in with. Revoking access is one click in eBay.

More on the eBay connector

eBay connector for claude.ai Wix + Claude Code Ecwid + Claude Code Etsy + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us