SellerSonar’s MCP connection lets you ask your AI assistant questions about the monitoring data in your SellerSonar account. You can review listing changes, Buy Box activity, prices, sellers, keyword rankings, reviews, and competitors. You can also ask the assistant to perform supported actions in SellerSonar, such as adding products to monitoring.

Connect SellerSonar from Claude’s connector directory or the shared ChatGPT and Codex plugin directory, then sign in to your SellerSonar account and approve access. For other AI applications, use the manual MCP setup below.

Before you start

You need:

  • An active SellerSonar account with MCP access enabled.
  • Access to Claude, ChatGPT, Codex, or another compatible AI application. Your account and workspace settings must allow the connection.
  • Tracked products, keywords, or competitors if you want to analyze existing monitoring data.

Available features, monitoring limits, and history depend on your SellerSonar plan. Use your primary account to manage connections; the MCP access settings page is not available to shared sub-users.

Connect to Claude

  1. Open Customize → Connectors in Claude.
  2. Click + and browse the connector directory.
  3. Find SellerSonar, open its page, and click Connect.
  4. On the SellerSonar authorization page, sign in to the account you want to use. Review the access request and click Connect.
  5. Return to your Claude conversation and enable SellerSonar under + → Connectors.

In Claude Team or Enterprise, an organization owner must enable the connector before members can use it. Each member then connects their own eligible SellerSonar account.

See Claude’s official connector guide for current interface details.

Connect to ChatGPT or Codex

ChatGPT and Codex share a public plugin directory, so you can use the same SellerSonar listing in both.

  1. Open the Plugins tab in the application. For ChatGPT on the web, you can also go directly to the plugin directory.
  2. Find SellerSonar and open its page.
  3. Select the + button to install it and follow the connection prompts.
  4. When the SellerSonar authorization page opens, sign in, review the access request, and click Connect. Authorization may be requested during installation or the first time you use SellerSonar.
  5. Start a new ChatGPT or Codex conversation and ask it to use SellerSonar. In ChatGPT, you can also type @ and select SellerSonar explicitly.

In Codex CLI, enter /plugins to open the plugin browser, install SellerSonar, and complete any connection prompts. Start a new CLI session before using it.

In a managed workspace, your administrator may need to allow the plugin before you can connect it. See OpenAI’s official plugin guide for current installation and workspace availability details.

Other AI applications and manual MCP setup

Use this method for other AI applications that support remote MCP connections with OAuth sign-in. The Codex IDE extension also uses this method.

Connect using the server URL

  1. Sign in to SellerSonar.
  2. Open User profile → MCP access.
  3. Copy the URL under MCP Server.
  4. In your AI application, add a remote MCP server and paste the URL. If asked for a transport, select Streamable HTTP.
  5. Follow the connection prompts. On the SellerSonar authorization page, sign in, review the access request, and click Connect.

The standard URL is https://app.sellersonar.com/mcp. Use the URL shown in your account if it differs.

Additional clients

Follow the instructions for your specific application:

Check that the connection works

With SellerSonar enabled in your conversation, ask:

Use SellerSonar to list my tracked products. Show each product’s ASIN, title, and marketplace. Check all result pages.

Look for a successful SellerSonar tool call and products that match your account. An empty list is valid if you have not added products yet.

You can also check User profile → MCP access → Active connections in SellerSonar. Click Refresh if needed.

What you can ask

Topic Example request
Listing changes “Show the listing changes recorded for my tracked products this week, grouped by ASIN.”
Buy Box “Which tracked ASINs lost the Buy Box today? Include the available prices and winning sellers.”
Sellers “Show new sellers detected this week. Compare them with my authorized seller list: [list].”
Keyword rankings “Which tracked keywords declined most this week? Show the dates, ASINs, and marketplaces.”
Reviews “Summarize the available one- and two-star reviews from the last 30 days. Group complaints by theme.”
Competitors “Summarize the price, ranking, and listing changes recorded for my tracked competitors this week.”

Specify the ASINs, marketplace, date range, and preferred format. Include your timezone when using “today” or similar periods.

The assistant uses the monitoring data and history available in SellerSonar. Ask for observation timestamps when freshness matters. Suggested causes of a Buy Box loss are interpretations; a newly detected seller is not automatically unauthorized.

Make changes in SellerSonar

Depending on your account access, the assistant can:

  • Add products to monitoring, including products with keywords or competitors.
  • Add tracked keywords.
  • Create product or keyword groups and add items to them.
  • Add comments to events or notifications.

For example:

Add ASIN [ASIN] in marketplace [marketplace] to my SellerSonar monitoring.

Create a product group named “Launch watch” and add these tracked products: [ASINs and marketplaces].

Replace the bracketed values with your own. Ask explicitly for the changes you want and review any approval requests in your AI application. Account limits still apply. These actions change SellerSonar data; they do not edit Amazon listings or Seller Central settings.

Data access and disconnecting

Your AI application receives the results of the SellerSonar tools it calls under your authorization. In addition to monitoring data, supported tools can return account and plan information, alert delivery settings, comments, and a limited catalog file preview. Review your AI provider’s data-handling settings before connecting.

To revoke access:

  1. Open User profile → MCP access in SellerSonar.
  2. Find the application under Active connections.
  3. Click Revoke and confirm.
  4. Remove the connection from your AI application if you no longer need it.

Disabling a connector in one conversation does not revoke account access. Revocation stops future requests through that authorization but does not erase information already included in conversations. To reconnect, repeat the sign-in and approval process.

Troubleshooting

  • SellerSonar is missing from the directory or cannot be installed: check that you are in the intended AI account or workspace. In a managed workspace, ask its administrator whether the connector is allowed.
  • MCP access is missing in SellerSonar: check that you are using the primary account and that it is active with MCP access enabled.
  • Sign-in or connection fails: check the selected SellerSonar account, then reconnect and finish the approval step. For manual setup, also check that you copied the complete MCP URL.
  • The installed plugin has no tools available: start a new conversation or CLI session and complete any outstanding SellerSonar sign-in prompts.
  • A feature is unavailable: check the error message and whether your SellerSonar plan includes that feature.
  • Results are empty or incomplete: confirm that the items are tracked and have data for the requested period. Ask for remaining result pages or narrow the request to a few ASINs.
  • Rate-limit error: wait and retry, or split the request into smaller batches.

For help, contact SellerSonar support with the AI application name, the failed step, and the exact error message. Include relevant ASINs, marketplaces, and dates.