Add Remote MCP

Add this Streamable HTTP endpoint to a compatible client:

https://ecommercedataapi.com/mcp

It exposes 49 tools: 45 individual business tools and the original 4 generic tools, plus 1 MCP Prompt named ecommerce-data-api. Business tools include amazon_asin_detail and amazon_asin_competitor; OCR file uploads remain REST only.

WorkBuddy: browser OAuth first

Follow the WorkBuddy setup steps. The connection needs only type: "http" and url; do not add an Authorization header, Client ID, or Client Secret. A compatible client automatically opens the browser for sign-in and approval.

On the authorization page, select an active existing key and confirm, or explicitly choose Create and authorize. A single existing key is preselected but still requires confirmation. The raw key is not sent to WorkBuddy.

If a previous configuration contains a fixed Authorization header, OAuth will not start. Remove only that header from this service and reconnect; if needed, clear only this connection's old authorization cache. Do not replace other MCP server entries.

Add it to ChatGPT web

1. Open ChatGPT web settings and enable Developer mode.
2. Add a remote MCP server with the URL above and choose OAuth authentication.
3. Sign in to Ecommerce Data API.
4. Select an existing key and confirm, or explicitly create and authorize a key. A single preselected key still requires confirmation.
5. Return to ChatGPT and start a new conversation.
6. Ask: “Use ecommerce_account to check my credits. Do not call paid data APIs yet.”

OAuth binds your account, the selected key ID, and its credential fingerprint; it does not send the raw API key to the client.

Tools and Prompt

After connecting, check that individual tools such as amazon_asin_detail appear. For a paid lookup, ask for the price and rating of Amazon US ASIN B08CK5Z5Q1. The original ecommerce_api_search, ecommerce_api_describe, ecommerce_api_call, and ecommerce_account remain available.

The ecommerce-data-api Prompt has the title Ecommerce Data API and an optional task argument of up to 4,000 characters. Selecting it loads instructions without data queries or charges. Slash-menu visibility depends on the client; natural-language tool calls do not require the Prompt.

Billing and access

MCP and REST share the account balance. Each data query consumes the credits listed in the API catalog, and one chat message may trigger several queries. Keys do not have independent permissions, budgets, or rate limits.

Resetting, deleting, or expiring the selected key invalidates access. Switching OAuth keys requires new authorization. Revoking the MCP connection does not delete or disable the REST key or stop direct access with it. Reset or delete the key to stop direct access. Failed paid requests are not automatically retried.

Alternatives and troubleshooting

• Only a Bearer Token field is available: use an active API key as a fallback. The client sends Authorization: Bearer <api-key> and stores the raw key. This mode does not open browser OAuth. Never put the key in the URL.
• No key is available during authorization: explicitly choose Create and authorize. No key is created merely by opening the page.
• OAuth fails: confirm Streamable HTTP, OAuth 2.1, and PKCE S256 support. Check the callback and connection state in the client; protocol compatibility alone does not establish a successful client authorization flow.
• No tools appear: reconnect, open a new conversation, and check server status.
• Insufficient credits: add credits and retry; paid calls are not automatically retried.

Local stdio still uses API-key configuration, not OAuth. Use CLI 0.2.2 or later for the updated tools. See the multi-platform guide for Hermes, WorkBuddy, and Claude Code.