ebay-mcp
ebay-mcp is a local Model Context Protocol (MCP) server (STDIO/optionally HTTP) that exposes ~325 tools for accessing eBay Sell REST APIs, including inventory, orders, marketing, analytics, and OAuth/token management. It provides an interactive setup wizard to configure eBay credentials and perform OAuth 2.0 to obtain/refresh user tokens.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Strengths/positives inferred from provided content: uses OAuth 2.0 with refresh token management; uses helmet (dependency listed) suggesting some HTTP hardening if HTTP transport is used; environment-variable based configuration via dotenv. Uncertainties/concerns: provided content does not show TLS requirements explicitly, how refresh tokens are stored/secured, whether logs redact secrets, or OAuth scope granularity. Secret handling and dependency hygiene can’t be verified from the excerpt alone.
⚡ Reliability
Best When
You want local, tool-based eBay automation through an MCP-capable AI client and you can securely manage OAuth credentials and run the server in your environment.
Avoid When
You need a hosted SaaS integration with centralized security controls, or you cannot handle secure storage of Client Secret/refresh tokens.
Use Cases
- • Build AI assistants that can manage eBay inventory (listings, offers, SKU/location mapping)
- • Automate order retrieval and fulfillment workflows (orders, refunds, disputes evidence)
- • Generate and manage marketing campaigns/promotions via AI
- • Query seller analytics/metrics and operational data for decision support
- • Perform eBay developer/admin tasks like checking rate limits or signing keys via tool calls
Not For
- • Replacing your own compliance, approvals, and business logic for high-risk actions (e.g., cancellations/refunds)
- • Unattended production workloads without monitoring and rate-limit/backoff controls
- • Apps that require a first-party, managed eBay integration (this is an unofficial third-party MCP server)
Interface
Authentication
README indicates automatic fallback between user-token authentication (higher rate limits) and client credentials. Specific OAuth scopes/granularity are not described in the provided content.
Pricing
This appears to be a local open-source package; costs primarily come from eBay API usage and your infrastructure/compute.
Agent Metadata
Known Gotchas
- ⚠ Running as a local MCP server means tool calls depend on correct local environment configuration (.env) and OAuth completion.
- ⚠ Some tools can trigger side effects (e.g., offers/fulfillment); ensure your agent has appropriate guardrails and you understand idempotency for each eBay endpoint.
- ⚠ Rate limit behavior depends on whether user tokens vs client credentials are used; tool actions may fail or slow down without backoff handling.
- ⚠ Large number of tools (~325) increases the chance of the agent invoking unintended endpoints; constrain/whitelist tools in the MCP client if possible.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ebay-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.