Lumitec Amazon

Connect your Amazon accounts to Claude

Set up the Lumitec Amazon MCPs in Claude Cowork or Claude Desktop โ€” about 5 minutes once you have your Amazon credentials in hand.

Prefer to skip the walkthrough? If you're comfortable editing a JSON config file, jump straight to the browser-based config generator.
๐ŸชŸ If you're on Windows, read this first. Three gotchas that bite every Windows user โ€” all solved below, but worth knowing up-front:

0Before you start

You'll need these four things ready before diving in. The Amazon credential gathering is the longest part โ€” usually 30โ€“60 minutes the first time if you've never set up an SP-API developer account.

1. Claude Cowork installed

If you don't have it yet, download from claude.com.

2. Node.js on your machine

Open PowerShell (Windows) or Terminal (Mac) and run:

node --version

If you see v20.x or higher, you're good. Otherwise install from nodejs.org/en/download โ€” pick the LTS installer, accept defaults, restart your terminal, and check again.

3. Your Lumitec access key

A short string starting with lk_. If you don't have one yet, email a.walters@lumitec.ai.

4. Your Amazon credentials

From the Amazon SP-API Developer Console and (optionally) the Advertising API Console:

FieldFormat
Client IDamzn1.application-oa2-client.โ€ฆ
Client Secretamzn1.oa2-cs.v1.โ€ฆ
Refresh TokenAtzr|โ€ฆ (region-locked)
Regioneu / na / fe
Primary Marketplace IDe.g. A1F83G8C2ARO7P (UK)
Seller IDStarts with A, ~14 chars

1Install the plugin

In Claude Cowork:

  1. Go to Settings โ†’ Plugins (or Customize โ†’ Personal plugins).
  2. Click Add marketplace.
  3. Paste this URL:
https://github.com/lumitecai/lumitec-cowork-plugin
  1. When lumitec-amazon appears, click Install.

2Run the setup skill

Open a new Cowork conversation and type:

Please set up Lumitec Amazon for me

Claude will take over and walk you through the rest. Expect roughly this sequence:

Using Claude Desktop instead of Cowork? The same skill works, but because Desktop doesn't have the VM tooling Cowork does, you'll copy-paste the generated JSON into your config file manually. Claude will give you the exact block and the file path. Or use the browser form as a shortcut.

3Restart Claude

After Claude confirms the config is saved:

  1. Find the Claude icon in your system tray (bottom-right of the taskbar on Windows โ€” you may need to click the ^ arrow to see hidden icons).
  2. Right-click the icon and select Quit. Just closing the window isn't enough โ€” it'll keep running in the tray.
  3. Reopen from the Start menu.

First launch after install takes about 10 extra seconds while a small helper is downloaded in the background. Subsequent launches are instant.

4Verify it works

Start a fresh conversation and ask:

Check my Amazon connections

You should see both MCPs report green. Try a few real queries to make sure data flows correctly:

?If something doesn't work

Claude says "Missing or invalid Lumitec key"

The key doesn't match what Lumitec issued. Email a.walters@lumitec.ai and we'll resend it.

Claude says "Failed to authenticate with Amazon"

One of your Amazon credentials is wrong, or the refresh token is for a different region than you selected. Refresh tokens are region-locked โ€” a token issued under EU marketplace access won't work with region: na. Start a new conversation and say "set up Amazon again" โ€” Claude will re-run the flow with fresh values.

The "approve directory access" dialog never appeared

Cowork's permission system can get stuck. Quit Cowork fully from the system tray, reopen, and say "continue setting up Amazon" in the same conversation.

Tools don't appear after restart

Cowork might still be running in the background. Check the system tray carefully โ€” right-click the Claude icon, click Quit, then reopen.

Windows: 'IwEBI...' is not recognized as an internal or external command

This is the refresh-token pipe-character issue. The setup skill ships a .cmd wrapper per MCP that quotes the headers properly. If you see this error, you're pointing claude_desktop_config.json at npx directly instead of at a .cmd file. Re-run "set up Amazon" in a new Cowork conversation and let the skill regenerate the config with the wrapper approach.

Windows: spawn npx ENOENT

Node.js isn't installed or isn't on your PATH. Install from nodejs.org, close and reopen your terminal, verify with node --version, then restart Claude.

Windows: edited config file but changes don't take effect

There are two possible config paths on Windows. If you installed Claude from claude.com, your config is at %APPDATA%\Claude\claude_desktop_config.json. If you installed from the Microsoft Store, it's at %LOCALAPPDATA%\Packages\Claude_<hash>\LocalCache\Roaming\Claude\claude_desktop_config.json. Check both; you were probably editing the wrong one.

Cowork: I clicked "Install" on the Amazon connector and got an OAuth error

Cowork's Personal Plugins UI shows a blue Install button on each connector card. Clicking it kicks off an OAuth flow that doesn't match how Lumitec's MCPs authenticate (per-request headers, not OAuth). Ignore that button entirely. Start a new chat and say "set up Lumitec Amazon" โ€” the skill drives the whole install for you.

Something else went wrong

Copy whatever Claude says back to a.walters@lumitec.ai and we'll diagnose it from there.

๐Ÿ”’What happens to your data

When you use an Amazon tool in Claude, your request goes: Claude โ†’ Lumitec's hosted MCP server โ†’ Amazon's API โ†’ back the same way. Your Amazon credentials travel with each request as HTTP headers โ€” Lumitec's server uses them only to make that one API call to Amazon on your behalf, then discards them from memory.