Remote MCP
Discover 49 Ecommerce Data API tools and connect through browser OAuth, with direct API key access available as a fallback.
Remote MCP
The same endpoint, https://ecommercedataapi.com/mcp, exposes 49 tools:
45 individual business tools and the original 4 generic tools, plus 1 MCP Prompt.
It uses Streamable HTTP. Browser OAuth is recommended for WorkBuddy and other
compatible clients; direct API key authentication remains available.
For copyable configuration and connection checks, see the WorkBuddy setup steps.
Tools and Prompt
Business tools appear individually in the MCP tool list. Names follow the canonical API URL, so you can select an operation directly:
| Tool | Corresponding REST operation |
|---|---|
amazon_asin_detail | POST /v1/amazon/asin/detail |
amazon_asin_competitor | POST /v1/amazon/asin/competitor |
Each business tool advertises its own input schema. Use the parameters shown by the client; the full operation descriptions are in the API catalog. OCR file uploads remain available through REST only and are not included in the 45 tools.
The original tools remain available for existing workflows:
| Tool | Purpose |
|---|---|
ecommerce_api_search | Search the API catalog |
ecommerce_api_describe | Inspect an operation and its parameters |
ecommerce_api_call | Call an operation using its code and input |
ecommerce_account | Check account credits |
For example: “Use amazon_asin_detail to look up Amazon US ASIN B08CK5Z5Q1
and return its price and rating.” This is a billable data query.
The retained MCP Prompt is named ecommerce-data-api, with the title
Ecommerce Data API. Its optional task argument accepts up to 4,000 characters.
Selecting it loads instructions without querying data or charging credits.
Whether it appears in a slash menu depends on the client; natural-language
tool requests also work without selecting the Prompt.
Connect with browser OAuth
- Add the production URL as an HTTP / Streamable HTTP MCP server. In WorkBuddy,
use
type: "http"andurl, without anAuthorizationheader, Client ID, or Client Secret. - A compatible client opens browser authorization automatically. Sign in to Ecommerce Data API.
- Select an active existing API key and confirm authorization, or explicitly choose Create and authorize on the authorization page.
- If there is only one existing key, it is preselected, but you still need to confirm. Return to the client after approval.
OAuth does not send the raw API key to the client. Review or revoke a connection
in MCP settings. If WorkBuddy already has a fixed
Authorization header, remove only that header from this service and reconnect.
If needed, clear only this connection's old authorization cache. Preserve all
other MCP server entries.
Billing and key lifecycle
MCP and REST share the account balance. Each data call consumes the credits listed in the API catalog; one chat request may cause several billable calls. API keys do not have separate budgets, permissions, or rate limits.
Resetting, deleting, or expiring the selected key invalidates access. Switching the key used by OAuth requires new authorization. Revoking an MCP connection does not delete or disable the REST API key and does not stop direct API key access. To stop that access, reset or delete the key. Failed paid requests are not automatically retried.
Other connection options
Direct API key access uses Authorization: Bearer <api-key>. The client stores
the key and does not start browser OAuth. Never put a key in the URL.
Local stdio also uses an API key; it does not become an OAuth connection.
Use CLI 0.2.2 or later for the updated tool list. See the
multi-platform guide for setup.
OAuth clients must support OAuth 2.1 with PKCE S256. A connection requests
ecommerce:tools offline_access for the Ecommerce Data API MCP resource.