Reference

Troubleshooting

Fix common Launch Fast MCP connection, access, sync, and empty-result issues.

Most Launch Fast MCP issues fall into one of five categories:

Category	What to check first
Claude is not connected to Launch Fast.	Connector settings, OAuth, server URL, or API key config.
The Launch Fast account does not have MCP access.	Plan entitlement, subscription status, and the account used during sign-in.
The relevant Amazon account is not connected.	Seller Central/SP-API or Amazon Ads in Settings -> Authentication.
Reporting data has not synced yet.	First sync, Amazon report availability, and reporting lag.
The query is too narrow or uses a date range with no data.	Date range, ASIN, SKU, campaign, marketplace, seller, account, profile, and connection filters.

Start with the simplest checks first.

Quick Checklist

Before debugging deeply, confirm:

Check	Why it matters
Launch Fast MCP is connected in Claude or your MCP client.	Claude cannot call tools until the connector is active.
You are signed in to the correct Launch Fast account.	OAuth and API keys are tied to one authenticated account.
Your Launch Fast plan includes MCP access.	MCP access is plan-gated.
The relevant Amazon connection exists in Settings -> Authentication.	Account tools need Amazon data connected inside Launch Fast.
Seller Central/SP-API is connected for sales, inventory, finance, and Brand Analytics tools.	These tools require seller-side Amazon reporting.
Amazon Ads is connected for Sponsored Products tools.	Ads tools require Amazon Ads reporting.
The first reporting sync has had time to finish.	New connections may not have queryable reports immediately.
Your query uses a date range where data exists.	Empty results often come from date windows with no synced data.
Your filters are not too narrow.	Exact ASIN, SKU, campaign, profile, or marketplace filters can exclude valid rows.

Claude Does Not Show Launch Fast Tools

What It Means

Claude may not have the Launch Fast connector enabled for the current chat, project, or workspace.

Common Causes

Cause	What to check
Launch Fast connector was not added.	Confirm the connector exists in Claude settings.
Connector was added but not enabled for the current chat.	Check the chat or project tool settings.
OAuth authorization did not finish.	Reconnect and complete the browser sign-in flow.
The MCP client needs to be restarted.	Restart developer clients after config changes.
The server URL was entered incorrectly.	Use the production server URL below.
API key configuration is missing or invalid.	Check the `X-LaunchFast-API-Key` header for developer clients.

What To Try

For Claude / Claude Desktop Connectors:

Step	Action
1	Open Claude connector settings.
2	Confirm Launch Fast is connected.
3	If needed, remove and reconnect Launch Fast.
4	Use the production server URL.
5	Sign in to Launch Fast again when prompted.
6	Start a new chat and ask a simple test prompt.

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

Test prompt:

Research the Amazon market for silicone spatulas.

For API-key clients:

Check	Expected value
MCP server URL	`https://launchfastlegacyx.com/api/mcp/server`
Header name	`X-LaunchFast-API-Key`
Client state	Restarted after config changes
API key	Active key generated from Launch Fast settings

Tools Are Disabled After Connecting

What It Means

The connector may be installed, but the authenticated Launch Fast account may not have MCP-enabled access.

Common Causes

Cause	What to check
The account is on a plan without MCP access.	MCP access is available on Growth and Scale entitlements.
Subscription is inactive or expired.	Confirm billing and subscription status in Launch Fast.
The wrong Launch Fast account was used during OAuth.	Sign out and reconnect with the intended account.
Account profile has not refreshed after plan changes.	Reconnect the Claude connector after changing plans.

What To Try

Step	Action
1	Open Launch Fast.
2	Confirm you are signed in to the same account used in Claude.
3	Check your plan and subscription status.
4	Confirm the account has Growth or Scale entitlement access.
5	If you recently changed plans, sign out and reconnect the Claude connector.

Prompt to ask Claude:

Check what Launch Fast MCP account data and tool access are available for my account.

"Please connect your amazon account on launchfast"

What It Means

The tool you asked for needs connected Amazon data that is not available for your Launch Fast account.

Which Connection Is Needed

Tool type	Required connection
Sales	Amazon Seller Central / SP-API
Inventory	Amazon Seller Central / SP-API
Finance	Amazon Seller Central / SP-API
Brand Query Report	Amazon Seller Central / SP-API with Brand Analytics access
Brand Search Terms Report	Amazon Seller Central / SP-API with Brand Analytics access
Brand Search Catalog Report	Amazon Seller Central / SP-API with Brand Analytics access
Amazon Ads Product Performance	Amazon Ads
Amazon Ads Targeting Performance	Amazon Ads
Amazon Ads Search Term Performance	Amazon Ads
Amazon Ads Campaign Performance	Amazon Ads
Amazon Ads Diagnostics	Amazon Ads; Seller Central/SP-API is optional for inventory/order context

What To Try

Step	Action
1	Open Launch Fast.
2	Go to Settings -> Authentication.
3	Connect or reauthorize the relevant Amazon account.
4	For sales, inventory, finance, or Brand Analytics, connect Seller Central/SP-API.
5	For Sponsored Products reports, connect Amazon Ads.
6	Wait for reporting data to sync.
7	Retry with a broad recent query.

Recovery prompt:

The tool says I need to connect my Amazon account. Explain which connection is required for this request and where I should connect it in Launch Fast.

Empty Results

What It Means

An empty result does not always mean the tool failed. It often means no synced data matched the date range or filters.

Common Causes

Cause	Example
Date range is outside available synced data.	Asking for older data than Launch Fast has imported.
ASIN or SKU had no matching rows.	No sales, inventory, finance, or ads activity for that product.
Campaign did not spend during the selected period.	Ads reports return no matching campaign rows.
Marketplace filter is wrong.	Product data exists in one marketplace, but the query filters another.
Seller, profile, account, or connection filter is too narrow.	The filter excludes the matching data source.
Brand Analytics data is unavailable.	ASIN, account, marketplace, or period has no report rows.
Amazon Ads report data has not synced yet.	Sponsored Products data is still importing.
Amazon has not made the report available yet.	Amazon-side reporting lag can delay availability.

What To Try

First, broaden the query:

Try the same analysis for the last 30 days and remove ASIN, SKU, campaign, account, profile, marketplace, seller, and connection filters.

Then narrow gradually:

Step	Narrowing sequence
1	Confirm a broad summary returns data.
2	Add the date range.
3	Add marketplace or profile if needed.
4	Add ASIN, SKU, campaign, or search term last.

Data Looks Outdated

What It Means

Launch Fast may be showing the latest data that has synced from Amazon, but Amazon reporting can lag.

Common Causes

Cause	Detail
First sync is still running.	New Amazon connections may take time to populate reports.
Amazon report availability is delayed.	Launch Fast can only sync data Amazon makes available.
Finance and settlement data often lags behind sales.	Finance reports may arrive later than order data.
Brand Analytics reports may update on a different schedule.	Brand reports can lag or use period-based availability.
Ads reporting may lag.	Sponsored Products data depends on Amazon Ads reporting availability.
Account was recently connected or reauthorized.	Sync queues may need time after authorization changes.

What To Try

Option	Why it helps
Wait for the first sync to finish after connecting.	Prevents testing before data is available.
Use a slightly older date range.	Avoids same-day reporting lag.
Try the last 7 or 30 days instead of today only.	Broadens the window to include synced rows.
Check whether other reports have fresher data.	Helps isolate report-specific lag.
Reauthorize the Amazon connection if it appears expired.	Refreshes access if the connection is stale.

Prompt:

The result looks outdated. Help me determine whether this is likely a sync delay, Amazon reporting delay, or a date range issue.

Wrong Account, Marketplace, Or Profile

What It Means

If you have multiple seller accounts, marketplaces, or Amazon Ads profiles, Claude may need a narrower filter.

Common Causes

Cause	Example
Multiple Seller Central accounts are connected.	Sales data may exist under a different `seller_id`.
Multiple Amazon Ads profiles are connected.	Campaigns may belong to a different `profile_id`.
Selected marketplace does not match the product.	The ASIN may sell in US but not another marketplace.
Campaign belongs to another ads profile.	Campaign ID/name lookup may fail under the wrong profile.
Seller Central and Amazon Ads accounts are not linked as expected.	Ads and seller-side inventory context may not align automatically.

What To Try

Ask for available account context first:

Show what Amazon accounts, marketplaces, and ads profiles are available in Launch Fast MCP.

Then retry with the right filter:

Run the same analysis for the correct Amazon Ads profile and US marketplace.

ASIN Or SKU Not Found

Common Causes

Cause	What to try
ASIN was mistyped.	Copy the ASIN from Amazon or from a broad Launch Fast result.
SKU differs from the label used in Amazon.	Search by SKU and ASIN separately.
One ASIN has multiple SKUs.	Use SKU for seller-side detail when needed.
Product had no activity in the selected period.	Broaden the date range.
Product exists in Seller Central but not in the selected report type.	Check a broader sales, inventory, or ads summary first.
Ads use an advertised SKU while sales are queried by ASIN.	Use Product Performance `top_products` before drilling in.

What To Try

Step	Action
1	Search by ASIN first.
2	Search by SKU if ASIN returns nothing.
3	Remove date filters.
4	Try a broader account summary to find the exact ASIN/SKU.
5	For ads, use Product Performance `top_products` first, then drill into the exact returned ASIN/SKU.

Prompt:

Find the closest matching ASIN or SKU from available sales, inventory, or ads data, then use that exact value for the detail lookup.

Campaign Not Found

Common Causes

Cause	What to try
Campaign ID was mistyped.	Search top campaigns first.
Campaign name is slightly different.	Search by similar campaign names.
Campaign belongs to another ads profile.	Remove `profile_id` or use the correct profile.
Campaign had no spend in the selected date range.	Broaden the date range.
Campaign is paused or archived and filtered out.	Remove status filters.
Amazon Ads data has not synced yet.	Wait for sync and retry.

What To Try

Show top campaigns for the last 30 days, then use the matching campaign_id for campaign_detail.

If using campaign name:

Find campaigns with names similar to "Silicone Spatula Exact" and summarize matching options.

Cause	What to check
Seller Central/SP-API is not connected.	Connect it in Settings -> Authentication.
Brand Analytics access is unavailable for the account.	Confirm the account has access to the relevant Amazon reports.
ASIN does not have data for the period.	Try a broader date range or different report period.
Marketplace filter is wrong.	Remove marketplace filter or use the correct marketplace ID.
Report period has no matching rows.	Try another period such as quarter where supported.
Data has not synced yet.	Wait for sync and retry.

What To Try

Try the Brand Analytics query over a broader date range and remove marketplace, seller, and connection filters.

If ASIN-specific:

Check whether this ASIN has any Brand Query Report or Brand Search Catalog Report data in the last quarter.

Cause	Result
Amazon Ads is connected, but Seller Central/SP-API is not.	Ads findings work, but inventory pressure is limited.
Seller account cannot be matched unambiguously to ads data.	Some inventory/order context may be missing.
Inventory data has not synced.	Inventory pressure findings may be incomplete.
Product identifiers do not align cleanly between ads and seller reports.	ASIN/SKU matching may be limited.

What To Try

Step	Action
1	Connect Seller Central/SP-API in Settings -> Authentication.
2	Wait for inventory and order data to sync.
3	Retry inventory pressure diagnostics.

Prompt:

Run Ads Diagnostics and explain which findings have seller inventory context and which do not.

Limit	Current value
Default MCP requests	60 requests/min
Amazon Ads reporting	120 reads/min per user
Amazon SP-API reporting	120 reads/min per user
Rank Tracker MCP tools	60 requests/min per user
Metadata/account status MCP requests	180 requests/min per user

Common Causes

Cause	Example
Too many MCP requests in a short period.	Repeated refreshes or tool retries.
Repeated Product Research or Keyword Research calls.	Many research-provider-backed calls in a row.
Repeated SellerSprite-backed calls.	Upstream provider limits apply to supported research tools.
A client retrying automatically.	Developer clients may retry failed requests.

What To Try

Option	Why it helps
Wait before retrying.	Allows rate limits to reset.
Ask broader questions instead of many small repeated requests.	Reduces total tool calls.
Reduce large batch workflows.	Keeps provider-backed calls under limits.
Avoid repeatedly refreshing the same research query.	Prevents redundant calls.

Prompt:

Summarize what we already know from the previous Launch Fast results instead of running the same tool again.

Cause	What to check
API key was copied incorrectly.	Copy the key again from Launch Fast settings.
API key was revoked.	Generate a new key.
Header name is missing or wrong.	Use `X-LaunchFast-API-Key`.
MCP client config was not restarted.	Restart after editing config.
Key belongs to a different Launch Fast account.	Generate the key from the intended account.

Correct Header

X-LaunchFast-API-Key: YOUR_API_KEY

What To Try

Step	Action
1	Open Launch Fast.
2	Go to Settings -> Authentication.
3	Create a new MCP API key.
4	Update the MCP client config.
5	Restart the client.
6	Keep the key private.

Common Causes

Cause	What to try
User signed into the wrong Launch Fast account.	Sign out and reconnect with the intended account.
Browser blocked the OAuth popup or redirect.	Allow the popup/redirect and retry.
Connector was already partially authorized.	Remove the connector and reconnect.
Session cookies are stale.	Use a new browser window.
Plan does not include MCP access.	Confirm Growth or Scale entitlement access.

What To Try

Step	Action
1	Sign out of Launch Fast and sign back in.
2	Remove the Launch Fast connector from Claude and reconnect.
3	Use a new browser window.
4	Confirm plan access.
5	Retry the connector flow.

Server URL:

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

Claude Gives A Generic Answer Instead Of Using Launch Fast

Common Causes

Cause	What to check
Connector is not enabled in the current chat.	Enable Launch Fast in Claude tool/connector settings.
Prompt does not clearly require Launch Fast data.	Ask Claude to use Launch Fast MCP explicitly.
Claude decided it could answer without a tool.	Specify that it should not answer from general knowledge.
Tool failed and Claude continued with general knowledge.	Retry after fixing the tool or connector issue.

What To Try

Ask explicitly:

Use Launch Fast MCP to research the Amazon market for silicone spatulas. Do not answer from general knowledge.

For account data:

Use Launch Fast MCP to analyze my connected Amazon sales data for the last 30 days.

Setup Test Prompts

Use these to verify each major tool group.

Area	Test prompt
Research	`Research the Amazon market for silicone spatulas.`
Rank Tracker	`Show my tracked ASINs.`
Seller Central / SP-API	`Summarize my Amazon sales for the last 7 days.`
Inventory	`Show low-stock inventory below 30 days of cover.`
Finance	`Summarize Amazon fees and settlement activity for the last 30 days.`
Brand Analytics	`Show Brand Query Report for ASIN B07HQM6NH8 over the last quarter.`
Amazon Ads	`Summarize my Sponsored Products performance for the last 30 days.`
Ads Diagnostics	`Scan my Sponsored Products data for wasted spend and harvest opportunities from the last 30 days.`

What Launch Fast MCP Cannot Do

Launch Fast MCP does not directly:

Cannot do	Boundary
Place Amazon orders	No purchasing actions are performed.
Create or edit Amazon listings	Listing changes must be made manually outside MCP.
Change prices	Pricing is not mutated by MCP tools.
Update inventory quantities	Inventory tools are reporting-only.
Create shipments	Fulfillment actions are out of scope.
Issue refunds	Customer/order actions are out of scope.
Contact customers	No customer communication is sent.
Create or modify Amazon Ads campaigns	Ads tools are reporting and diagnostics only.
Change bids or budgets	Campaign settings are not edited.
Add or remove keywords or targets	Targeting changes must be made manually.
Add negative keywords	Claude may recommend negatives, but does not add them.
File trademarks or patents	IP Check is a research aid, not a filing tool.
Contact suppliers	Supplier Research does not message suppliers.

Claude can recommend actions, but users must make account changes manually outside the MCP tools.

When To Contact Support

Contact Launch Fast support if:

Issue	When to escalate
OAuth repeatedly fails.	Reconnect attempts do not complete successfully.
A paid account should have MCP access but tools remain disabled.	Plan status looks correct but MCP access is unavailable.
Amazon connections show active but all reports are empty after waiting for sync.	Broad queries still return no data.
API keys fail after regeneration.	New keys still fail with correct header config.
The same tool fails consistently across broad queries.	The issue is not caused by narrow filters.
Synced Amazon data appears missing or stale.	Data remains unavailable after normal reporting lag.

Support:

https://launchfastlegacyx.com/contact

Privacy:

https://launchfastlegacyx.com/privacy

Troubleshooting

On this page