Set up the Lumitec Amazon MCPs in Claude Cowork or Claude Desktop โ about 5 minutes once you have your Amazon credentials in hand.
|) that cmd.exe interprets as a shell pipe. We ship a .cmd wrapper template that wraps it correctly.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.
If you don't have it yet, download from claude.com.
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.
A short string starting with lk_. If you don't have one yet, email a.walters@lumitec.ai.
From the Amazon SP-API Developer Console and (optionally) the Advertising API Console:
| Field | Format |
|---|---|
| Client ID | amzn1.application-oa2-client.โฆ |
| Client Secret | amzn1.oa2-cs.v1.โฆ |
| Refresh Token | Atzr|โฆ (region-locked) |
| Region | eu / na / fe |
| Primary Marketplace ID | e.g. A1F83G8C2ARO7P (UK) |
| Seller ID | Starts with A, ~14 chars |
In Claude Cowork:
https://github.com/lumitecai/lumitec-cowork-plugin
Open a new Cowork conversation and type:
Claude will take over and walk you through the rest. Expect roughly this sequence:
lk_โฆ valueAfter Claude confirms the config is saved:
First launch after install takes about 10 extra seconds while a small helper is downloaded in the background. Subsequent launches are instant.
Start a fresh conversation and ask:
You should see both MCPs report green. Try a few real queries to make sure data flows correctly:
The key doesn't match what Lumitec issued. Email a.walters@lumitec.ai and we'll resend it.
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.
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.
Cowork might still be running in the background. Check the system tray carefully โ right-click the Claude icon, click Quit, then reopen.
'IwEBI...' is not recognized as an internal or external commandThis 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.
spawn npx ENOENTNode.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.
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'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.
Copy whatever Claude says back to a.walters@lumitec.ai and we'll diagnose it from there.
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.