MCP server
Connect Claude or another compatible AI assistant to sellerfox to analyze your workspace data in chat. The MCP server provides 22 read-only tools: the assistant can read data but cannot create, change, or delete workspace data.
Requirements
- You have a confirmed sellerfox account that is neither blocked nor deleted.
- You are an active Owner or Admin in every workspace you want to connect. Viewer and External cannot use MCP.
- An Owner or Admin enables MCP in each workspace. You then personally approve the workspaces for your connection.
Connect an MCP client
These steps take you from enabling access in sellerfox to asking your first question in Claude. The original screenshots show the English sellerfox and Claude interfaces.
1. Enable MCP access in sellerfox
- As an Owner or Admin, open Settings → Integrations in each workspace and select “Enable access” next to “MCP access”.
- Confirm the disclosures in the dialog, then select “Enable”.
The dialog explains that the connected AI client or its provider may process responses, including outside the EU and EEA. sellerfox does not control that processing. You also confirm that you have authority to share the workspace's data – including the seller's consent if you work for an agency – and that the use complies with the applicable Amazon, seller, and agency agreements.
2. Add sellerfox to Claude
Where you add the connector depends on your Claude access:
| Claude access | Where to add the connector |
|---|---|
| Individual | Open Customize → Connectors, select “+”, then “Add custom connector”. |
| Team or Enterprise | An Owner or Primary Owner of your Claude organization opens Organization settings → Connectors and selects Add → Custom → Web. This step adds the connector for the organization. |
The next two screenshots show the Team and Enterprise entry point:
Name the connector “Sellerfox” as shown and enter this server URL:
https://api.sellerfox.com/mcpSave with “Add”. On Team and Enterprise, each member then connects with their own sellerfox account.
3. Connect and approve workspaces
- In Claude, open Customize → Connectors and select your sellerfox connector.
- Select “Connect”. The sellerfox sign-in page opens in your browser.
- Sign in with your sellerfox account and select “Continue”.
- Select at least one available workspace that Claude may read. You can approve several workspaces.
- Confirm with “Authorize” and return to Claude. When using Claude Desktop, you will see this connection confirmation:
If a workspace is missing or unavailable for selection, check its MCP setting, your active membership, and your role there.
4. Set tool permissions
In Claude, open Customize → Connectors again and select sellerfox. Choose which tools Claude may use and when it should ask before retrieving data. Your Claude organization's policies may restrict the choices available to you.
5. Check the connection in chat
- Open a chat in Claude.
- Select + → Connectors beside the message field and enable sellerfox for this conversation.
- Ask:
Which sellerfox workspaces can you access?
Claude can now list the workspaces available to this connection. Use the name of the workspace you want to analyze in your next questions.
Connect another MCP client
Use the same server URL in a client that supports remote MCP servers with browser-based sign-in. Enable MCP in sellerfox first, then approve the workspaces during sign-in. The steps for adding the server depend on the client.
Start an analysis
Name the workspace, marketplace, and date range in your question. Then explain what you want to compare or understand, for example:
- "Summarize sales, advertising spend, and profit over the last 30 days for my workspace on the German marketplace. Check data availability first and flag any gaps."
- "Which products had the highest sales on the German marketplace last month? Compare them with the previous month."
- "How have the organic rankings of my tracked keywords changed over the last four weeks?"
Check data readiness before analysis
Ask the assistant to check for connection problems and unfinished data imports before analyzing your figures. These issues can make the numbers for your chosen period look too low.
You can include the check in your question:
Check my workspace's data first. Are there any connection problems or imports still running? What are the latest sales and advertising report dates for each marketplace? Take these findings into account in the analysis.
sellerfox provides known connection problems, import progress, and the dates of the oldest and newest available sales, traffic, and advertising reports for each marketplace. When reading the answer:
- There may be gaps between report dates. The oldest and newest reports do not establish that data exists for every day in between. A response without warnings does not confirm complete data either.
- Missing reports can produce a result of 0. If reports are missing for a period, a result of 0 does not automatically mean you had 0 sales or 0 advertising spend.
The report-date check does not cover SQPR, keyword-ranking, or profit data.
For SQPR, the assistant can only analyze weekly or monthly reports that have already been loaded. Ask it to state the actual period used: SQPR queries always cover complete report weeks or months. You can check and load missing reports in the Search Term Analyzer.
See Data refresh for when each data source is updated.
Profit queries and cost attribution
For total profit, ask about the whole workspace without product or marketplace filters. More detailed analyses have these limits:
- Product filters exclude costs that cannot be attributed to the selected products. A marketplace filter excludes manual costs assigned to the whole workspace.
- Advertising costs and the resulting net profit cannot be attributed by SKU. Analyze by ASIN or marketplace for these figures.
- Use the totals provided. Unassigned costs are already included; subtotals and individual cost components cannot simply be added together.
- Refunds count in the period when they are settled. Ongoing imports or missing cost of goods sold can still affect the result.
See Profit Tracking for how profit and costs are calculated.
Manage existing connections
In sellerfox, open “Account: Connected Apps” under “User settings”. This lists your connections and the workspaces you have shared.
- Use “Manage” to change the workspace selection. After you remove a workspace, the client cannot access it on the next request.
- Use “Revoke” to end the connection. You must connect and authorize the client again before it can retrieve more data.
If you are removed from a workspace and rejoin later, you must approve it for the connection again.
Owners and Admins currently cannot view or individually revoke other users' personal MCP connections in the dashboard. They can block access for the entire workspace through its MCP setting. Removing a member from the workspace also immediately ends their access to that workspace's data through the MCP client.
You must authorize a connection again after no more than 180 days.
Disable MCP for the entire workspace
Select “Disable access” under Settings → Integrations to block all MCP requests for that workspace immediately. Personal connections and workspace approvals remain in place. After MCP is enabled again, valid connections can resume access if membership, role, and approval still permit it.
Call logs
sellerfox stores MCP call logs for up to 180 days. For workspace requests, they record the time, client, tool, requested workspace, and whether an error occurred. These logs are not currently available in the dashboard.
Requirements for each data request
sellerfox checks five security requirements on every request for workspace data. Your connection must also be valid and must not have been revoked.
- Your sellerfox account is available. Your sellerfox account is confirmed and neither blocked nor deleted.
- Your membership is active. You are an active member of the requested workspace. A pending invitation is not enough.
- Your role allows MCP. You are an Owner or Admin in that workspace. Viewer and External cannot use MCP.
- MCP is enabled in the workspace. An Owner or Admin has enabled “MCP access” under Settings → Integrations.
- You have approved the workspace for this connection. You explicitly selected the workspace when connecting the MCP client or later through “Manage”.
As soon as any of these requirements is no longer met, sellerfox blocks the next data request. This also applies to MCP clients that are already connected.
Limits
Many requests in a short time can temporarily reach a usage limit. If your MCP client reports too many requests, wait for the indicated time and try again.
For missing workspaces, connection problems, or empty results, see Troubleshooting → MCP server.
If Claude reports a connection issue
The message "Connection issue" indicates a connection problem. The screenshot below shows an error state. Check the server URL; if the message persists, contact support.
Tool overview
The tools cover workspaces, products, marketplaces, keywords, SQPR, events, Best Seller Rank (BSR), and Profit Tracking. This list shows what data the assistant can retrieve.
| Tool | What it returns | Feature |
|---|---|---|
| Workspaces and KPI definitions | ||
get_workspaces | Lists the workspaces this connection can access. | MCP server |
get_workspace_info | Shows marketplaces, currency, time zone, data availability, and connection or import problems. | MCP server |
get_kpi_definitions | Lists available KPIs, their names, units, and supported analyses. | MCP server |
| Products | ||
get_products | Finds products by name, ASIN, or SKU, with an optional marketplace filter. | Products & product lists |
get_product_kpis | Returns aggregated KPIs for one or more products over a date range. | Products & product lists |
get_product_trends | Returns time-series values for one KPI across one or more products. | Products & product lists |
| Marketplaces | ||
get_marketplace_kpis | Returns aggregated KPIs at the marketplace level. | Marketplaces dashboard |
get_marketplace_trends | Returns time-series marketplace KPIs. | Marketplaces dashboard |
| Keywords | ||
get_keywords | Lists keywords tracked in the workspace. | Keywords |
get_keyword_kpis | Returns aggregated KPIs for tracked keywords over a date range. | Keywords |
get_keyword_trends | Returns time-series ranking data for tracked keywords. | Keywords |
get_products_by_keyword_kpis | Returns the products that rank for one tracked keyword, along with their KPIs. | Keywords |
| Search Query Performance (SQPR) | ||
get_sqpr_kpis | Returns Search Query Performance Report KPIs aggregated by search query. | SQPR reports |
get_sqpr_trends | Returns time-series SQPR data for selected search queries. | SQPR reports |
get_products_by_search_query_kpis | Returns workspace products with loaded SQPR data for an exact search query, along with selected SQPR KPIs. | SQPR reports |
| Events | ||
list_events | Lists listing, catalog, Buy Box loss, Seller Central account status, and custom events, sorted from newest to oldest. | Events |
| Best Seller Rank (BSR) | ||
get_bsr_trends | Shows the daily Best Seller Rank (BSR) history for a product on a marketplace. | BSR Explorer |
get_bsr_ranks | Compares the latest available Best Seller Rank (BSR) readings and rank changes across products. | BSR Explorer |
| Profit Tracking | ||
get_profit_summary | Returns revenue, costs, and profit for a date range, with their shares of net revenue. | Profit Tracking |
get_profit_breakdown | Breaks down revenue, refunds, advertising, fees, and other costs into their components. | Profit Tracking |
get_profit_by_product | Compares profit KPIs by marketplace, parent ASIN, child ASIN, or SKU, with totals and unassigned costs. | Profit Tracking |
list_income_expenses | Lists manual and Amazon-derived income and expenses in their original currency. These entries are only part of the profit calculation. | Profit Tracking |
Related
- Permissions – workspace access and roles.
- Data security – data sharing and retention.
- Webhooks – send selected data to your own endpoint on a schedule.
- Claude help: Custom connectors – current Claude menus and requirements.