MCP Server

Authentication

Claude and Codex desktop use browser sign-in, also called OAuth. You sign in on Launch Fast and authorize the selected tools. Your AI app receives authorization to call those tools; you do not give it your Launch Fast password.

In Claude, open Customize → Connectors → Add custom connector. In Codex desktop, open Settings → Plugins → Add → Add MCP server.
Enter the Launch Fast server URL and follow the browser sign-in prompts.
On Launch Fast, choose the permissions you need and select Continue.
Complete any authenticator verification on Launch Fast, then return to your AI app.

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

See Getting Started for the exact fields and permission labels.

Authenticator App For Amazon Tools

Private Amazon reports require an authenticator app. This includes sales, inventory, finances, Brand Analytics, and Sponsored Products reports. Product and market research do not require an Amazon connection or this Amazon verification.

Open Launch Fast Settings → Authentication.
Under Authenticator app, choose Set up authenticator if needed and finish the prompts.
Open Settings → Amazon to connect Amazon accounts. If you see Verify and unlock, enter your authenticator code on the verification page.
When authorizing your AI app, select the Amazon permissions you need and complete verification if prompted.

Amazon Seller Central and Amazon Ads are separate connections. Signing in to the AI connector does not create either connection. See sales and ads prerequisites.

When Verification Is Needed Again

For private Amazon reports, the renewal period depends on how you connected:

Claude and Codex desktop (browser sign-in): renew your Amazon tool authorization every 365 days. Reopen Launch Fast's sign-in flow in your AI app, review the permissions, and complete authenticator verification.
API-key clients: verify access to Amazon reports with your authenticator every 30 days. If a tool returns mfa_required, open its step_up_url on Launch Fast, enter your authenticator code there, and retry. This renews verification; you do not need to generate a new API key just because verification is due.

You may need to verify sooner after changing account security, reconnecting Amazon, or adding Amazon permissions. Follow the prompt if this happens. These periods apply to access to private Amazon reports; product and market research do not require Amazon verification.

Access And Usage

MCP requires active paid access with a Growth or Scale entitlement. Starter does not include MCP. An older subscription may have a different billing name; check the access attached to your account in Settings → Billing.

MCP does not provide a separate unlimited research allowance. Research, supplier searches, and rank tracking follow your Launch Fast account's allowances and capacity. One conversation can make several tool calls.

Ask the assistant:

Read my Launch Fast account status. Show my MCP access, available usage allowances, reset dates, and rank tracker capacity. If account status cannot be read, say so rather than guessing.

The account-status resource requires Research and insights permission. If you only selected Amazon reports, add this permission through authorization to let the assistant read account status.

Short-term request limits also apply. Tools can have different limits, and shared service limits can apply even before your personal allowance is used. Follow the retry time returned by Launch Fast; see Rate Limit Exceeded.

API Keys For Developer Clients

Use an API key only when your client requires one. Claude and Codex desktop users should use the browser flow above.

Open Launch Fast Settings → Amazon and unlock it if prompted.
Find MCP API keys and choose Generate new key.
Name the key, choose Generate key, and save it privately when shown.
Send it in the following header. See the developer configuration example.

X-LaunchFast-API-Key: YOUR_API_KEY

API-key management is on the Amazon tab, but product and market research still do not require a Seller Central or Ads connection. The settings page can require authenticator verification before you manage keys.

Keep Access Private

Enter passwords and authenticator codes only on Launch Fast's HTTPS sign-in or verification page. Do not put them in AI messages, screenshots, or support tickets. Keep API keys out of public repositories. If a key is exposed, revoke it in MCP API keys and replace it.

The Amazon reporting tools are read-only. They do not change bids, budgets, campaigns, listings, prices, or inventory. Manage rank tracking is a separate permission that changes tracked products inside Launch Fast.