Seamlessly integrate eBay's APIs into your AI assistant workflow. This MCP server enables Claude Desktop, Cursor, Cline, and other AI tools to discover and call eBay marketplace APIs directly.
- 🔍 REST API Access – Search, browse, and call eBay REST APIs (via OpenAPI specs) using plain language
- 💬 Natural language interface – Just describe what you want; no need to memorize endpoints
- 🔑 Simplified setup with automatic token management – Just provide Client ID and Client Secret; the server handles OAuth token generation and refresh every ~2 hours
- 🗝️ Dual token mode – Application tokens for public data, User tokens for private data
- ⚡ MCP Prompt support – Enhanced AI assistant integration for REST APIs
- Node.js 22 or higher - Verify:
node --version - eBay Developer Account - Sign up at developer.ebay.com
Sandbox Environment Not Supported
This release does not officially support the eBay sandbox environment. While the EBAY_API_ENV configuration exists, we don't support sandbox for now.
Production Environment Restrictions
- REST APIs: Only GET requests are supported (read operations only)
- Write operations: POST, PUT, DELETE are not available in production
This MCP server is designed for safe, read-only access to production eBay data. Sandbox support and write operations may be added in future releases.
Choose the setup option that works best for you:
- Option A (Recommended): Use the published npm package — no build step required
- Option B: Clone and build from source — useful if you want to modify or contribute to the server
Skip straight to getting credentials — no build step needed.
Client ID & Client Secret:
- Get from: developer.ebay.com/my/keys
Required Scopes:
- Depends on which APIs you need to access
- Reference: OAuth Scopes Documentation
Refresh Token (optional, only for User Token mode):
- Reference: OAuth Authorization Code Grant
Add this configuration to your MCP client's config file. The server runs via npx — no installation or build step needed.
User Token Mode (for accessing private user data):
{
"mcpServers": {
"ebay-api": {
"command": "npx",
"args": ["-y", "@ebay/npm-public-api-mcp"],
"env": {
"EBAY_CLIENT_ID": "your_client_id",
"EBAY_CLIENT_SECRET": "your_client_secret",
"EBAY_TOKEN_TYPE": "user",
"EBAY_REFRESH_TOKEN": "your_refresh_token",
"EBAY_API_ENV": "production"
}
}
}
}Note: In User Token Mode, scopes are inherited from your refresh token. You don't need to configure EBAY_REQUIRED_SCOPES.
Application Token Mode (for accessing public data):
{
"mcpServers": {
"ebay-api": {
"command": "npx",
"args": ["-y", "@ebay/npm-public-api-mcp"],
"env": {
"EBAY_CLIENT_ID": "your_client_id",
"EBAY_CLIENT_SECRET": "your_client_secret",
"EBAY_REQUIRED_SCOPES": "your_required_scopes",
"EBAY_TOKEN_TYPE": "application",
"EBAY_API_ENV": "production"
}
}
}
}Note: EBAY_REQUIRED_SCOPES is optional; omit it to default to https://api.ebay.com/oauth/api_scope.
Claude Code:
Use claude mcp add to register the server. Use --scope user for all projects or --scope project for the current project only.
User Token Mode:
claude mcp add --scope user ebay-api \
-e EBAY_CLIENT_ID=your_client_id \
-e EBAY_CLIENT_SECRET=your_client_secret \
-e EBAY_TOKEN_TYPE=user \
-e EBAY_REFRESH_TOKEN=your_refresh_token \
-e EBAY_API_ENV=production \
-- npx -y @ebay/npm-public-api-mcpApplication Token Mode:
claude mcp add --scope user ebay-api \
-e EBAY_CLIENT_ID=your_client_id \
-e EBAY_CLIENT_SECRET=your_client_secret \
-e EBAY_TOKEN_TYPE=application \
-e EBAY_REQUIRED_SCOPES=your_required_scopes \
-e EBAY_API_ENV=production \
-- npx -y @ebay/npm-public-api-mcpRestart your MCP client to load the server.
Use this option if you want to modify the server or contribute to the project.
git clone https://github.com/eBay/npm-public-api-mcp.git
cd npm-public-api-mcp
# Install dependencies and build
npm install
npm run buildRequirements: Node.js 22+
Same as Option A — see Step 1 above.
Same as Option A, but replace command and args with your local build path:
"command": "node",
"args": ["/absolute/path/to/npm-public-api-mcp/dist/index.js"]For Claude Code, replace -- npx -y @ebay/npm-public-api-mcp with -- node /absolute/path/to/npm-public-api-mcp/dist/index.js. All environment variables remain the same.
Restart your MCP client to load the server.
| Variable | Required | Description |
|---|---|---|
EBAY_CLIENT_ID |
✅ Yes | eBay application Client ID |
EBAY_CLIENT_SECRET |
✅ Yes | eBay application Client Secret |
EBAY_TOKEN_TYPE |
No | "application" (default) or "user" |
EBAY_REFRESH_TOKEN |
Conditional | Required when EBAY_TOKEN_TYPE="user" |
EBAY_REQUIRED_SCOPES |
No | OAuth scopes (Application Token mode only). For multiple scopes, separate them with spaces, e.g., "https://api.ebay.com/oauth/api_scope https://api.ebay.com/oauth/api_scope/sell.inventory" |
EBAY_API_ENV |
No | "production" (sandbox not supported) |
This server exposes two primary tools and one MCP prompt to your AI assistant.
Searches eBay's OpenAPI specifications using a natural language prompt. Use this to explore available APIs, look up endpoint parameters, or find the right API for a task.
Find eBay APIs related to product listings
What parameters does the Browse API's getItem endpoint require?
Which API should I use to search for items by keyword?
Executes actual calls to eBay's APIs and returns live marketplace data. Typically used after query_ebay_api has identified the right endpoint.
Search for iPhone 15 listings on eBay and show me the top 5 results
Get details for eBay item ID 123456789
Show me eBay's taxonomy categories for electronics
You can ask in natural language — the AI selects and sequences the tools automatically.
This server also registers one MCP prompt to help the client turn broad user requests into the right tool calls.
Accepts the user's original request as user_input and returns guidance that helps the MCP client decide when to use query_ebay_api, when to use call_ebay_api, and how to phrase discovery queries.
Typical use cases:
- Convert abstract requests into concrete eBay API actions
- Decide whether to search API specifications first or invoke a known endpoint directly
- Improve the natural-language prompt sent to
query_ebay_api
Conceptually, the prompt tells the client to:
- inspect the user's request
- choose between
query_ebay_apiandcall_ebay_api - use descriptive discovery prompts when searching for an API
- proceed immediately with the most suitable approach
This prompt is registered under the name interpret_user_request in the MCP server and is intended for MCP clients that support prompt discovery and execution.
| Agent | How to invoke |
|---|---|
| Claude Code | Slash command: /mcp__ebay-api__interpret_user_request |
| GitHub Copilot | Slash command: /mcp.ebay-api.interpret_user_request |
Prompt support depends on the MCP client integration. If prompts are not exposed, use query_ebay_api and call_ebay_api directly.
| Mode | Use case | Requirements |
|---|---|---|
| User Token | Private user data (inventory, orders, account info) | Client ID, Client Secret, Refresh Token — scopes inherited from the refresh token |
| Application Token | Public marketplace data | Client ID, Client Secret, optional EBAY_REQUIRED_SCOPES |
Both modes handle token refresh automatically. For the OAuth flows behind each mode, see Authorization Code Grant and Client Credentials Grant.
- ✅ Never commit credentials to version control
- ✅ Use environment variables or secure vaults for production
- ✅ Rotate Client Secrets periodically
- Refresh tokens are long-lived — store them securely
- Application tokens auto-expire after ~2 hours (the server handles refresh)
- Never share tokens publicly or in screenshots
MCP Server Not Appearing:
- If using Option A (npx): verify your Node.js version is 22+ and that
npxis available - If using Option B (source build): verify
dist/index.jsexists (runnpm run build) and check the absolute path in your config - Restart your MCP client
Authentication Failed (401):
- Verify credentials are correct
- For application token mode, check
EBAY_REQUIRED_SCOPESincludes necessary permissions - For user token mode, ensure refresh token is valid
Token Retrieval Failed (IDE launched from GUI):
- IDEs launched from the GUI (e.g., VS Code, Cursor) may not inherit shell environment variables, causing credentials to be unresolved and token requests to fail.
- Fix (quickest): Hardcode the credential values directly in the config file — just do not commit them to version control.
- Fix (alternative): Launch your IDE from the terminal so it inherits the shell environment. VS Code and Cursor support this natively after a one-time CLI install from the Command Palette.
API Call Failed:
- This release only supports production environment
- Production only supports GET requests for REST APIs (read operations)
- Check your eBay account has proper API access
If you previously used an earlier version of this MCP server, here is what has been added in this release:
- Automatic Token Management – Tokens were previously managed manually; the server now handles refresh automatically
- Simplified Setup – Previously required pre-generated OAuth tokens; now only Client ID and Client Secret are needed (the server handles token generation)
- Dual Token Mode – Application and User token modes are now configurable via environment variables
- MCP Prompt Support – Prompts are now supported for REST APIs
- 🔐 Get eBay Credentials - Client ID & Secret
- 📚 eBay API Documentation - Complete API reference
- 🔧 MCP Protocol - Learn about MCP
Happy testing! 🎉
Apache 2.0 - See LICENSE for more information.