Claude + eBay: What the Integration Can (and Can't) Do in 2026
Sort of — eBay publishes an official MCP server, but it’s a local developer tool, not a Claude connector. @ebay/npm-public-api-mcp is a stdio npm package you run on your own machine with your own OAuth token — it does API discovery, documentation browsing, and live production/sandbox calls against eBay’s APIs. There’s no eBay entry in Claude’s connectors directory and no hosted remote MCP. It’s built for developers exploring eBay’s APIs, not as a turnkey seller assistant. And one thing to get out of the way immediately: effective February 20, 2026, eBay’s user agreement bans buy-for-me AI agents from completing checkout without eBay’s permission. Anything you build here should be seller-side. That’s also where the real value is.
Here’s exactly what exists, how to set it up, where the limits bite, and what to use if you want selling work that runs on its own.
What eBay’s official MCP server actually is
Run EBAY_CLIENT_TOKEN=... npx @ebay/npm-public-api-mcp@latest and add it to Claude Desktop or Claude Code as a local MCP server, and Claude gets three things:
- API discovery — find the right eBay API and operation for a task.
- Doc browsing — pull eBay’s API documentation into the conversation.
- Live calls — execute real requests against production or sandbox with your OAuth token.
Notice what that list is: a developer tool for working with eBay’s APIs, made official by eBay. It’s excellent if you’re building on the eBay platform. It is not “connect Claude to my eBay store” in the way the WordPress.com connector is — there’s no OAuth-and-go, no packaged seller tools, and it lives on your laptop. A community alternative, YosefHayim/ebay-mcp, packages 322 tools over the Sell APIs — explicitly unofficial, so vet accordingly.
Meanwhile eBay’s own AI is seller-facing and substantial: the magical listing tool builds listings from photos (title, category, item specifics, pricing recommendations), rebuilt on an agentic architecture in late 2025, with 10M+ sellers having used at least one AI feature. That lives inside eBay and doesn’t talk to Claude.
The buying ban, in plain terms
Effective February 20, 2026, eBay’s user agreement prohibits LLM agents and bots from completing checkout without eBay’s permission — eBay is building its own agentic shopping and partner integrations instead. So “have Claude snipe auctions for me” or “have an agent buy underpriced listings” isn’t a gray area anymore; it’s against the user agreement. Seller-side automation through the official developer APIs is unaffected. Every workflow in this post is seller-side, and that’s the standard you should hold any eBay AI tool to.
What the Sell APIs make possible
Behind an eBay Developers Program account (application review, then OAuth 2.0 user tokens per seller), the API surface for sellers is genuinely strong:
- Fulfillment — orders and shipping fulfillments.
- Inventory — SKUs, offers, and locations.
- Marketing — promotions and ads.
- Analytics — traffic reports (impressions, views, conversion).
- Finances — payouts and transaction fees.
- Browse — search and pricing data from the buy side (for research, not for buying).
Best of all: real push triggers. Platform Notifications and the newer event Notification API deliver order and listing events to your endpoint — order-driven workflows don’t need polling. One operational gotcha: user access tokens expire in ~2 hours (refresh tokens last ~18 months), so anything long-running needs proper refresh handling.
Through the MCP server, Claude can call all of this — inside a conversation you start. Which is the shape of the limit.
The limits that actually matter
- It’s a dev tool on your laptop. The official MCP server is local stdio with your token in an environment variable. No hosted connector, no directory entry, nothing your non-technical VA could switch on.
- No triggers, no monitoring. eBay’s notification APIs push events, but Claude has nowhere to receive them. MCP tools run inside a conversation you start — no “when an order lands, draft the buyer message,” no returns-deadline watching.
- No buying, period. Per the February 2026 user agreement, agents don’t check out on eBay. Don’t build it, don’t buy tools that claim it.
- Laptop-bound for anything scheduled. The nearest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events.
So Claude is great for “explore eBay’s APIs and query my seller account right now” and not built for “run my eBay operation while I’m sourcing inventory.”
If you want eBay selling work that runs on its own: Carly
Selling on eBay is event-driven by nature — orders, returns, offers, payout mismatches — and eBay’s APIs push those events in real time. The missing piece is something standing on the other end to act. That’s past what a local MCP dev tool is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat. eBay connects to Carly via your own API key — paste your eBay developer credentials on carlyassistant.com/integrations — and it works like any native connection (all seller-side, fully within eBay’s rules):
- When a new order lands, a packing summary plus a drafted buyer thank-you with shipping ETA; high-value orders flagged for signature confirmation.
- Every morning, a returns-and-cancellations digest with recommended responses and deadline countdowns.
- Repricing scout: competing listings for your tracked SKUs pulled via Browse, price changes proposed — applied to your offers only after you approve.
- Every Monday, a traffic report from Sell Analytics (impressions → views → conversion) naming the three listings most worth reworking, plus payout reconciliation from Finances.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
- Actually sends — drafts and sends email across Gmail and Outlook, updates records, manages tasks.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (eBay’s local MCP) | Carly | |
|---|---|---|
| Explore eBay APIs and docs | Yes (its real strength) | Not the point |
| Query orders, inventory, analytics | Yes (in a chat, with your token) | Yes |
| Acts on order/return events | No | Yes (push notifications) |
| Drafts buyer messages on its own | No | Yes |
| Buys items at checkout | No — banned by eBay’s user agreement (Feb 20, 2026) | No — banned; seller-side only |
| Works while laptop is closed | No (local stdio) | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with eBay’s MCP is a developer console for eBay’s APIs. Carly is a teammate that runs the seller side of the shop as events happen.
Frequently Asked Questions
Does Claude work with eBay?
Partially. eBay publishes an official MCP server (@ebay/npm-public-api-mcp), but it’s a local stdio developer tool — API discovery, doc browsing, and live calls with your own OAuth token — not a connector in Claude’s directory and not a hosted remote MCP. It only works inside a conversation you start, on the machine where it’s running.
Can Claude buy things on eBay for me?
No — and don’t try to make it. Effective February 20, 2026, eBay’s user agreement prohibits buy-for-me AI agents from completing checkout without eBay’s permission. Seller-side automation through the official developer APIs remains fully allowed; that’s where Claude and Carly both belong.
How do I connect Claude to eBay?
Join the eBay Developers Program (application review), get an OAuth token, then run EBAY_CLIENT_TOKEN=... npx @ebay/npm-public-api-mcp@latest and add it to Claude Desktop or Claude Code as a local MCP server. Note user tokens expire in about 2 hours, so you’ll re-authenticate for longer sessions.
What if I want new orders and returns handled without me in the chat?
That’s outside what a local MCP tool does — eBay pushes order events via its notification APIs, but Claude can’t receive them. Carly connects via your eBay developer credentials, listens for events 24/7 in the cloud, drafts buyer messages, and sends the emails — seller-side only. AI agents start at $35/month.
More: Claude + Etsy · Claude + Amazon · Claude + Shopify · Claude + Stripe · Claude Cowork alternatives
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
