MCP Platform Setup

Use the production MCP endpoint:

https://ecommercedataapi.com/mcp

It uses Streamable HTTP and exposes 49 tools: 45 individual business tools and the original 4 generic tools, plus 1 MCP Prompt. Business tool names derive from canonical API URLs, for example amazon_asin_detail and amazon_asin_competitor. OCR file uploads remain REST only.

Which connection should I use?

OAuth clients need OAuth 2.1 with PKCE S256. Direct API key access remains a fallback for clients that only accept a fixed Bearer Token.

ChatGPT web

1. Open ChatGPT settings and enable Developer mode.
2. Add a remote MCP server at the production URL and choose OAuth.
3. Sign in to Ecommerce Data API.
4. Select an active key and confirm, or explicitly choose Create and authorize. A single existing key is preselected but still requires confirmation.
5. Return to ChatGPT, start a new conversation, and ask: Use ecommerce_account to check my credits. Do not call paid data APIs yet.

Hermes

Add a remote server, choose Streamable HTTP, enter the production URL, and choose OAuth / browser authorization when the client offers it. Sign in, select or create and authorize a key, confirm, and refresh the connection.

If Hermes only accepts a fixed Bearer Token, use the direct API key fallback described below. Protocol compatibility alone does not establish that a particular Hermes build has completed the OAuth flow.

WorkBuddy

WorkBuddy's preferred remote configuration is browser OAuth. Configure only:

{
  "mcpServers": {
    "ecommerce-data-api": {
      "type": "http",
      "url": "https://ecommercedataapi.com/mcp"
    }
  }
}

Do not add Authorization, Client ID, or Client Secret. In a compatible client, browser authorization starts automatically. Sign in, select an active key and confirm, or explicitly click Create and authorize. A single key is preselected but still requires confirmation. The raw key is not sent to WorkBuddy.

The user configuration is ~/.workbuddy/mcp.json; Windows uses %USERPROFILE%\\.workbuddy\\mcp.json. Project configuration is .workbuddy/mcp.json. Add only this server entry to an existing mcpServers object. Do not replace other MCP configurations.

If an old WorkBuddy entry has a fixed Authorization header, OAuth will not start. Remove only that header for this service and reconnect. If needed, clear only this connection's old authorization cache. Do not clear other MCP caches.

WorkBuddy direct API key fallback

Use this only when the client has no browser OAuth mode:

{
  "mcpServers": {
    "ecommerce-data-api": {
      "type": "http",
      "url": "https://ecommercedataapi.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Keep the key out of the URL and local documentation. This fallback stores the raw key in the client and does not provide a browser authorization connection.

After connecting, confirm that individual tools such as amazon_asin_detail and the generic ecommerce_api_search, ecommerce_api_describe, ecommerce_api_call, and ecommerce_account are visible. The retained Prompt is named ecommerce-data-api, titled Ecommerce Data API, with optional task up to 4,000 characters. Selecting it only loads instructions; it does not query data or charge credits. Slash-menu visibility depends on the client, and natural-language requests remain available.

Claude Code remote OAuth

claude mcp add --transport http ecommerce-data-api https://ecommercedataapi.com/mcp

Open /mcp, choose browser authorization, sign in, select or create and authorize a key, confirm, and return to Claude Code.

Claude Code local stdio

The local installer and stdio connection still use an API key, not OAuth:

curl -fsSL https://ecommercedataapi.com/install.sh | bash -s -- --yes --only claude-code

Enter the key in the installer's local prompt. Use CLI 0.2.2 or later, then run ecomdata doctor and ecomdata mcp status. Remote URL users do not need the CLI.

Billing and key lifecycle

MCP and REST share the account balance. One chat request may trigger several billable data queries. Keys have no separate budgets, permissions, or rate limits. Resetting, deleting, or expiring the selected key invalidates access; switching an OAuth key requires new authorization.

Revoking an MCP connection does not delete or disable the REST key and does not stop direct API key access. Reset or delete the key to stop that access. Failed paid requests are not automatically retried.

See the official WorkBuddy connector guide and MCP guide.