The eBay MCP server — give Claude, Cursor, and any AI assistant full access to eBay's Sell APIs. 322 tools for inventory, orders, marketing, and analytics, running locally with your own keys.
Unofficial, open-source project — not affiliated with, authorized, or endorsed by eBay Inc.
English · 简体中文 · Español · Português (BR) · 日本語 · 한국어 · Français · Deutsch · Русский
eBay MCP is a local Model Context Protocol server that connects AI assistants — Claude Desktop, Claude Code, Cursor, Cline, Windsurf, Zed, Continue.dev, Roo Code, and Amazon Q — directly to eBay's Sell APIs. It exposes 322 tools spanning 100% of eBay's Sell API surface (270 unique endpoints) for inventory management, order fulfillment, promoted-listings marketing, analytics, and developer tooling. Everything runs on your machine over STDIO or local HTTP — no cloud relay, and your eBay credentials never leave your computer.
Disclaimer: Unofficial, third-party project — not affiliated with or endorsed by eBay Inc. Provided "as is" without warranty. You are responsible for complying with eBay's API License Agreement and data-handling requirements, keeping your credentials secure, and staying within rate limits. Test in sandbox before production. See LICENSE, SECURITY.md, and EBAY_COMPLIANCE.md.
- Features
- eBay MCP vs. the raw eBay API
- One-click AI setup
- Quick start
- Demo
- Configuration
- Available tools
- Interactive UI (MCP Apps) — beta
- Usage examples
- Logging & troubleshooting
- FAQ
- Contributing
- Resources
- License
- Contributors
- 322 eBay API tools — 100% coverage of the eBay Sell APIs across inventory, orders, marketing, analytics, metadata, taxonomy, and developer tooling.
- 9 AI clients, auto-configured — Claude Desktop, Cursor, Zed, Cline, Continue.dev, Windsurf, Roo Code, Claude Code CLI, and Amazon Q Developer.
- OAuth 2.0 built in — full user-token management with automatic refresh, and smart fallback from user tokens (10k–50k req/day) to client credentials (1k req/day).
- Resilient by default — automatic retry with exponential backoff on
429rate limits, and consistent, loud error surfacing. - Type-safe — TypeScript end to end, Zod-validated tool inputs, and OpenAPI-generated types.
- Local-first & private — runs over STDIO or local HTTP; your credentials and data never leave your machine.
- Sandbox and production — switch environments with a single variable.
- One-command setup —
npm run setupconfigures credentials, OAuth, and your MCP client, with a browser auto-opened for the OAuth flow. - Well tested — 1,000+ automated tests run in CI on every change.
Both talk to the same eBay endpoints — the difference is everything you'd otherwise build yourself.
| eBay MCP Server | Raw eBay REST API | |
|---|---|---|
| Interface | Natural language through your AI assistant | Hand-written HTTP requests and JSON parsing |
| OAuth & token refresh | Built in, with automatic refresh | You implement and maintain it |
| Rate-limit handling | Automatic retry with exponential backoff | Manual 429 handling and backoff |
| Input validation | Zod schemas + TypeScript types on every tool | None — you validate your own payloads |
| Setup | One wizard (npm run setup) |
Per-call auth, headers, and marketplace wiring |
| AI client support | 9 clients auto-configured | Not applicable |
| API coverage | 322 tools across 100% of the Sell APIs, ready to call | Build each request from the docs |
| Hosting | Runs locally, no cloud relay | Your own infrastructure |
Let your AI assistant set this up for you. Copy the prompt below and paste it into Claude, ChatGPT, or any AI assistant with MCP support.
Click to copy the AI setup prompt
I want to set up the eBay MCP Server for my AI assistant. Please help me:
1. Install the eBay MCP server:
npm install -g ebay-mcp
2. I need to configure it for [Claude Desktop / Cursor / Cline / Zed / Continue.dev / Windsurf / Claude Code CLI / Amazon Q] (choose one)
3. My eBay credentials are:
- Client ID: [YOUR_CLIENT_ID]
- Client Secret: [YOUR_CLIENT_SECRET]
- Environment: [sandbox / production]
- Redirect URI (RuName): [YOUR_REDIRECT_URI]
Please:
- Create the appropriate config file for my MCP client
- Set up the environment variables
- Help me complete the OAuth flow to get a refresh token for higher rate limits
- Test that the connection works
If I don't have eBay credentials yet, guide me through creating a developer account at https://developer.ebay.com/
- Create a free eBay Developer Account.
- Generate application keys in the Developer Portal.
- Save your Client ID and Client Secret.
npm install -g ebay-mcp # from npm (recommended)Or from source:
git clone https://github.com/YosefHayim/ebay-mcp.git
cd ebay-mcp && npm install && npm run buildnpm run setupThe wizard configures your eBay credentials, sets up OAuth (for higher rate limits), auto-detects and configures your MCP client, and saves everything automatically.
Restart your MCP client (Claude Desktop, etc.) and start managing eBay through your AI assistant.
📸 Visual setup walkthrough (eBay Developer Portal)
The setup wizard (npm run setup) handles OAuth automatically. Here's where to find your credentials in the eBay Developer Portal:
Step 1 — In the Developer Portal, copy your App ID (Client ID) and Cert ID (Client Secret):
Step 2 — In your app's User Tokens settings, copy the RuName (eBay Redirect URL):
Step 3 — Run npm run setup. It opens your browser for OAuth login and guides you through eBay sign-in:
Step 4 — Paste the authorization code from the callback URL when prompted:
The wizard exchanges the code for tokens, saves them, and configures your MCP client. You now have user-token authentication (10k–50k requests/day instead of the default 1k/day).
See the eBay MCP Server in action with Claude Desktop:
video-tutorial.mp4
📖 Full reference — every environment variable, OAuth step, and scope — is in the Configuration Guide.
npm run setupwrites the.envfor you; the variables below are for reference.
EBAY_CLIENT_ID=your_client_id
EBAY_CLIENT_SECRET=your_client_secret
EBAY_ENVIRONMENT=sandbox # or "production"
EBAY_REDIRECT_URI=your_runame
EBAY_MARKETPLACE_ID=EBAY_US # default marketplace (overridable per tool)
EBAY_CONTENT_LANGUAGE=en-US # default request content language
EBAY_USER_REFRESH_TOKEN=your_token # for higher rate limits
EBAY_MCP_UI=on # interactive MCP Apps views (beta); "off" forces plain JSON| Mode | Daily limit | Best for | Setup |
|---|---|---|---|
| Client credentials (default) | 1,000 req/day | Development, testing | Automatic with Client ID + Secret |
| User token (recommended) | 10k–50k req/day | Production, high volume | OAuth via npm run setup |
User-token limits vary by account tier (Individual 10k · Commercial 25k · Enterprise 50k+). On a 429, the server retries with exponential backoff and surfaces the error. See the Configuration Guide and OAuth Quick Reference for details, and monitor usage in the Developer Portal.
Auto-configured by npm run setup. Requires Node.js ≥ 18 and MCP protocol 1.0+ over STDIO (default) or HTTP.
| Client | Platform | Config path |
|---|---|---|
| Claude Desktop | macOS, Windows, Linux | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Cursor IDE | macOS, Windows, Linux | ~/.cursor/mcp.json |
| Zed Editor | macOS, Windows, Linux | ~/.config/zed/settings.json |
| Cline | VS Code extension | ~/...globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json |
| Continue.dev | VS Code, JetBrains | ~/.continue/config.json |
| Windsurf (Codeium) | macOS, Windows, Linux | ~/.codeium/windsurf/mcp_config.json |
| Roo Code | VS Code extension | ~/...globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json |
| Claude Code CLI | Terminal | ~/.claude.json |
| Amazon Q Developer | AWS | ~/.aws/amazonq/mcp.json |
322 tools, 100% Sell API coverage, organized by category. Each link points to the tool definitions and handlers in src/tools/categories/:
| Category | What you can do |
|---|---|
| Account | Business, fulfillment, payment, and return policies; programs; subscriptions; sales tax |
| Inventory | Inventory items, offers, locations, item groups, bulk operations, SKU/location mapping |
| Fulfillment | Orders, shipping, refunds, disputes, payment-dispute evidence |
| Marketing | Promoted-listings campaigns, ads, promotions, bidding, bulk operations |
| Analytics | Traffic reports, seller standards, customer-service metrics |
| Communication | Buyer–seller messaging, negotiations, notifications, feedback |
| Metadata | Return policies, sales-tax jurisdictions, automotive compatibility |
| Taxonomy | Category trees, item aspects, item conditions |
| Trading (legacy XML) | Fixed-price listing create, revise, relist, end |
| Developer | Rate limits, signing keys, client registration |
| Token Management | OAuth URL generation and token management |
Example tools: ebay_get_inventory_items, ebay_get_orders, ebay_create_offer, ebay_get_campaigns, ebay_get_oauth_url.
For the complete machine-readable index, see llms.txt.
Beta — this feature is new and evolving alongside the MCP Apps spec, and host support is still rolling out. It is opt-in and falls back to plain JSON, so it never breaks existing clients. Toggle it with
EBAY_MCP_UI(see Configuration).
On hosts that support MCP Apps, common read tools render their results as interactive views instead of raw JSON — a sortable table, a detail card, or a chart — using the host's own theme. Everywhere else, the exact same tools return plain JSON, so nothing breaks. It is built on the official MCP Apps SDK (@modelcontextprotocol/ext-apps), the extension that lets MCP servers ship interactive UI to conversational clients.
- Opt-in and host-gated. Views are advertised only to clients that announce the MCP Apps capability (e.g. Claude). Hosts without it (e.g. Cursor) silently get JSON.
- Kill-switch. Set
EBAY_MCP_UI=offto force plain JSON everywhere, even on capable hosts. - Token-cheap. Each view's HTML is fetched once by the host out of band (never into the model's context); the model only ever sees a one-line summary plus the structured data it would have received anyway.
- Read-only. Views only ever trigger read tools (drill into a row, page, refresh) — they never mutate your eBay data.
13 core-workflow tools opt in today, across three archetypes:
| Archetype | Tools |
|---|---|
| Table | ebay_get_orders, ebay_get_shipping_fulfillments, ebay_get_offers, ebay_get_inventory_items, ebay_get_inventory_locations, ebay_get_payment_dispute_summaries |
| Card | ebay_get_order, ebay_get_offer, ebay_get_inventory_item, ebay_get_payment_dispute, ebay_get_seller_standards_profile |
| Chart | ebay_get_traffic_report, ebay_get_customer_service_metric |
The views build into self-contained HTML with npm run build (or npm run build:ui); they ship in the published package and load with no network access of their own.
Common tasks, phrased as you'd ask your AI assistant:
- Set up OAuth — "Help me set up OAuth for my eBay account." → generates an authorization URL via
ebay_get_oauth_url, then configures the refresh token. Unlocks 10k–50k req/day. - Manage inventory — "Show me all my active listings." →
ebay_get_inventory_itemsreturns SKUs, quantities, and status. - Process orders — "Get all unfulfilled orders from the last 7 days." →
ebay_get_orderswith date and fulfillment-status filters. - Create campaigns — "Create a promoted-listing campaign for electronics." →
ebay_create_campaignand related marketing tools. - Bulk operations — "Apply a 10% discount to all 'Vintage Watches' items." →
ebay_get_inventory_items+ebay_update_offeracross matches.
- Logging — Winston-based, written to stderr (MCP-safe) with optional file output. See docs/logging.md.
- Troubleshooting — server not appearing, auth errors, rate limits, empty results. Start with
npm run diagnose, then see docs/troubleshooting.md.
A local Model Context Protocol server that exposes 322 tools covering 100% of eBay's Sell APIs (270 endpoints) to AI assistants — inventory, order fulfillment, marketing, analytics, and developer tools.
No. This is an unofficial, third-party open-source project. It is not affiliated with, authorized, or endorsed by eBay Inc.
Nine clients are auto-configured by npm run setup: Claude Desktop, Cursor, Zed, Cline, Continue.dev, Windsurf, Roo Code, Claude Code CLI, and Amazon Q Developer. Any MCP-compatible client can connect.
Yes. It works with Claude Desktop and Claude Code out of the box, with Cursor and other MCP-enabled IDEs, and with any assistant that supports the Model Context Protocol. The one-click setup prompt above works with ChatGPT and other assistants too.
Interactive MCP Apps views only appear on hosts that announce the capability (e.g. Claude); other clients get the same data as plain JSON. Also confirm you have not set EBAY_MCP_UI=off and that the views are built (npm run build runs build:ui).
322 tools across 270 unique endpoints — 100% of eBay's Sell APIs.
Yes. It is released under the MIT license.
It runs entirely on your machine over STDIO (or local HTTP). There is no cloud relay — your eBay credentials never leave your computer.
Node.js ≥ 18, a free eBay Developer Account (Client ID + Client Secret), then run npm run setup.
Client credentials (the default) allow about 1,000 requests/day. Authenticating with a user token via OAuth raises this to 10,000–50,000 requests/day depending on your account tier.
Yes. Switch with the EBAY_ENVIRONMENT variable (sandbox or production).
Credentials are stored locally in your .env file and used only to call eBay directly. See SECURITY.md and EBAY_COMPLIANCE.md.
You interact in natural language through your AI assistant. OAuth token management, automatic retries with backoff, and type-safe Zod validation are built in. See the comparison table above.
Yes. Fixed-price listing create, revise, relist, and end operations are supported through the Trading API tools.
Complete the OAuth flow with npm run setup to authenticate with a user token (10k–50k requests/day instead of the default 1k).
TypeScript and Node.js (ESM), using the official MCP SDK, Zod for validation, and OpenAPI-generated types.
Run npm install -g ebay-mcp@latest (or npm update -g ebay-mcp).
No. "Runs locally" means the server process runs on your machine — it still needs an internet connection and valid credentials to reach eBay's live APIs.
Contributions welcome. Fork → branch → add tests → npm run check && npm test → commit with Conventional Commits → open a PR.
- Working on the codebase or with a coding agent? Start with AGENTS.md — build/test commands, module map, and the add-an-endpoint workflow.
- Full guidelines: CONTRIBUTING.md.
- eBay Developer Portal — API docs and credentials
- eBay API License Agreement — terms and compliance
- eBay Data Handling Requirements — data protection and privacy
- MCP Documentation — Model Context Protocol spec
- OAuth Quick Reference — scopes, troubleshooting, examples
- eBay API Status — official status page (also via the
ebay_get_api_statustool and the in-repo snapshot) - CHANGELOG.md · SECURITY.md · CODE_OF_CONDUCT.md
- Issue Tracker — bug reports and feature requests
MIT — see LICENSE.
Thanks to everyone who has helped make this project better! 🎉
Support this project · Created by Yosef Hayim Sabag
eBay MCP server · Model Context Protocol for eBay Sell APIs · connect Claude, Cursor, and any AI assistant to eBay inventory, orders, marketing, and analytics.