Troubleshooting

Start With The Symptom

Server URL:

https://launchfastlegacyx.com/api/mcp/server

Tools Are Disabled After Connecting

1. Open Launch Fast Settings → Billing and check the account's access. Growth and Scale include MCP; Starter does not. Older billing names may differ.
2. Confirm you used the same Launch Fast account during your AI app's browser sign-in.
3. Check the selected permissions. A connection authorized only for research will not provide private Amazon reports.
4. After correcting access, reopen Launch Fast's authorization flow in your AI app and retry.

If access still looks wrong, contact support. Do not upgrade again just to test a connection issue.

mfa_required

The request needs authenticator verification. For private Amazon reports, API-key verification renews every 30 days; Claude and Codex desktop authorization renews every 365 days. Security changes, Amazon reconnection, or additional permissions can require verification sooner.

1. Check Settings → Authentication → Authenticator app in Launch Fast. Choose Set up authenticator if needed.
2. For Claude or Codex desktop, follow the reauthorization prompt or reopen Launch Fast's sign-in flow from the app's connector/server settings. Review all permissions needed for the request and verify on Launch Fast.
3. For an API-key client, open the error's step_up_url on Launch Fast, enter the authenticator code there, and retry.

Never paste an authenticator code into the AI conversation. See Authentication for the separate authorization paths.

Connection Needs To Be Reconnected

Check which connection failed before reconnecting it:

1. If the error refers to Seller Central or Amazon Ads, open Launch Fast Settings → Amazon. Unlock it if prompted and use Reconnect for the affected account.
2. Complete Amazon's authorization and allow syncing to resume.
3. If the error refers to your AI app's Launch Fast authorization, reopen that app's Launch Fast sign-in flow instead.
4. Retry the original report with the same account and dates.

Please Connect Your Amazon Account On Launch Fast

Your AI app can be connected to Launch Fast while the required Amazon account is missing.

1. Open Settings → Amazon and choose Verify and unlock if shown.
2. Use Connect Amazon seller or Connect Amazon Ads, as appropriate. They are separate connections.
3. Wait for the initial sync and check readiness.
4. Reauthorize Launch Fast in your AI app if the relevant permissions were missing, then retry.

Product and market research do not require these Amazon connections.

Empty Results

Missing or unsynced data must not be reported as zero sales or zero spend. An empty result can also mean the selected filters matched no rows.

1. Check the required account is Connected in Settings → Amazon.
2. Check sync status and available report dates. Up to 60 minutes is the initial-sync estimate, not a completion guarantee.
3. Confirm the seller account, marketplace, and Ads profile match your request.
4. Try a broader completed date range. Remove product or campaign filters one at a time, while keeping the intended account and marketplace clear.
5. Ask the assistant to distinguish missing coverage from a confirmed zero in an available report.

Use Launch Fast to check why this report is empty. Show the requested dates, available coverage, account, marketplace, and sync information. Keep different accounts separate. Do not interpret unavailable data as zero activity.

Data Looks Outdated

Launch Fast reports the data it has received from Amazon. A connected account or a recent sync does not guarantee every report is current.

1. Check Last sync for Seller Central and the profile status for Ads in Settings → Amazon.
2. If Ads shows Starting, Loading history, Scheduled, or Syncing, allow the import to progress. Check again for Synced and its timestamp.
3. Ask for the latest available report date and any sync warnings returned by the tool.
4. Compare a completed, slightly older date range. Keep reporting gaps visible in the answer.

Sales, finance, and Brand Analytics reports can arrive on different schedules. Ads-attributed orders and sales can be revised after the click date, so recent spend without attributed sales does not by itself prove wasted spend. Compare the same dates, marketplace, currency, and attribution window when checking Amazon's own reports.

If the page reports a failed sync, follow its recovery message. Contact support if data remains unavailable or progress stalls; repeatedly reconnecting a healthy account will not make Amazon release reports sooner.

Wrong Account, Marketplace, Or Profile

1. Ask the assistant to identify the seller account, marketplace, and Ads profile represented in the returned data.
2. Choose the account you intended and repeat the query for that account and date range.
3. Keep results from different marketplaces and currencies separate.

Do not remove all account filters and treat the combined result as one store's performance.

ASIN Or SKU Not Found

1. Check the identifier against your listing. ASINs and seller SKUs are different identifiers.
2. Confirm the account, marketplace, and date range.
3. Ask for a broader product summary, then use an exact identifier returned by that report.
4. If it is still missing, check report coverage. Do not silently substitute a similar product.

Campaign Not Found

1. Confirm the Amazon Ads profile and campaign name or ID.
2. Ask for campaigns available in a broader completed period.
3. Select the exact matching campaign from the results and retry. Check whether a status filter excluded it.

Brand Analytics Data Missing

1. Check Seller Central is connected and the corresponding Brand Analytics permission was authorized.
2. Confirm your Amazon account has access to that report for the marketplace and product.
3. Check the report period and sync status. Try another supported, completed period.

Brand Analytics is not available for every account, product, or period. Missing access or coverage is not zero demand.

Ads Diagnostics Has Limited Inventory Context

1. Select Performance diagnostics together with its required Sales and orders and Inventory permissions when authorizing Launch Fast.
2. For inventory-aware findings, connect both Seller Central and Amazon Ads in Settings → Amazon.
3. Check sales and inventory have synced and can be matched to the advertised products.
4. Ask the assistant to label findings that lack seller context.

Basic Sponsored Products performance reports need Amazon Ads. Diagnostics can return limited findings when seller data is unavailable, but its required seller permissions still apply to OAuth authorization.

Rate Limit Exceeded

Short-term request limits are separate from your plan's usage allowances. They vary by tool, and shared service or provider limits may also apply. A larger plan allowance does not remove request limits.

1. Follow the retry time in the error, if provided.
2. Stop repeated refreshes or automatic retries while waiting.
3. Ask the assistant to summarize results already returned before making another request.
4. If the error says an allowance is exhausted, check your account's usage and reset date instead of retrying immediately.

Summarize the Launch Fast results already returned in this conversation. Do not call the same tools again yet.

Invalid API Key

This section is only for developer clients using API keys. Claude and Codex desktop browser sign-in does not require a key.

1. Check the URL and the header name X-LaunchFast-API-Key.
2. In Launch Fast Settings → Amazon → MCP API keys, check that the key is active and belongs to the intended account.
3. If the key was revoked, lost, or exposed, generate a replacement and update the client privately.
4. Reload the client's MCP configuration and retry.

OAuth Sign-In Fails

1. Confirm the server URL matches the one at the top of this page.
2. Check the browser opened Launch Fast and that you are signing in to the intended account.
3. Allow the sign-in window or redirect if your browser blocked it.
4. Complete permission selection and any authenticator prompt, then return to the AI app.
5. If the attempt expired, start a fresh authorization attempt from the AI app.

If a permission is unavailable, check the related Amazon connection first. See the desktop setup steps.

The Assistant Gives A Generic Answer

Ask explicitly:

Use Launch Fast to review my Amazon sales for the last 7 complete days. Actually call the relevant tool. State the account and exact dates returned. If the tool fails or data is missing, explain that instead of answering from general knowledge.

Check the app's tool activity and the returned result. A plausible answer with specific numbers is not proof that Launch Fast was called. If no call appears, check that Launch Fast is enabled for this conversation.

What Launch Fast MCP Cannot Do

Amazon reporting tools are read-only. They cannot change bids, budgets, campaigns, keywords, listings, prices, or inventory; place orders; issue refunds; or contact customers and suppliers. Recommendations must be reviewed and carried out separately in the appropriate application.

Rank Tracker management can change tracked products inside Launch Fast. IP screening is a research aid, not legal clearance or a guarantee that a product is safe to sell.

When To Contact Support

Contact Launch Fast support if sign-in repeatedly fails, expected MCP access is missing, or a connected account's reports remain unavailable after checking sync and report coverage.

Include the AI app, tool/error name, time of failure, requested dates, and the non-sensitive sync status. State whether the issue affects research, Seller Central, or Ads. Do not send passwords, authenticator codes, or API keys. See the Privacy Policy.