catalog-cli-pro — Claude Code MCP server: Amazon catalog audits
An MCP server that runs 14 listing quality checks on an Amazon catalog. Point it at a CLR file and read the issues.
claude mcp add catalog-cli-pro -e CATALOG_API_KEY=<CATALOG_API_KEY> -- npx -y @bwb03/catalog-cli-proWhat catalog-cli-pro does
catalog-cli-pro plugs an agent into Amazon catalog auditing. The checks match the catalog CLI: missing mandatory attributes, banned characters in titles, bullet formatting, product type mismatches, products that should be variations. One check, mobile-title-readiness, flags titles past 75 characters and hands back the first 75 characters, the overflow and the significant terms, which is what you need before rewriting.
Seven MCP tools ship with it: catalog_scan, catalog_scan_summary, catalog_check, catalog_seller_listing_fetch, catalog_seller_listing_diff, catalog_list_queries, catalog_schema. The fetch tool pulls live Seller Central listing JSON for an ASIN; the diff tool lines that JSON up against a row in your CLR. Seller Central cookies never leave your machine — pass them with --cookie, --cookie-file or CATALOG_SELLER_CENTRAL_COOKIE.
You need CATALOG_API_KEY set, or the server will not start. A hosted option at $9.99/mo adds persistent storage and removes the scan cap. Locally it runs through npx. Incoming requests are validated with Pydantic, so malformed JSON and path traversal get rejected before any work happens.
What it helps with
- surface mandatory attributes that listings are missing
- catch banned characters and emojis inside bullet points
- list titles over 75 characters ahead of Amazon's mobile update
- diff a live listing against its Category Listing Report row
- export audit results as JSON for downstream tooling
Example prompts for the agent
- Run
catalog scanonmy-catalog.xlsxand show me only the error-level issues - Check the titles with
mobile-title-readinessand list the ones over 75 characters - Diff the live listing
B000TEST01against my CLR file and show what changed
How to install catalog-cli-pro
Platform CLI
claude mcp add catalog-cli-pro -e CATALOG_API_KEY=<CATALOG_API_KEY> -- npx -y @bwb03/catalog-cli-proReplace <…> with your own values
Platform CLI
codex mcp add catalog-cli-pro --env CATALOG_API_KEY=<CATALOG_API_KEY> -- npx -y @bwb03/catalog-cli-proReplace <…> with your own values
Config file
{
"mcpServers": {
"catalog-cli-pro": {
"command": "npx",
"args": [
"-y",
"@bwb03/catalog-cli-pro"
],
"env": {
"CATALOG_API_KEY": "<CATALOG_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"catalog-cli-pro": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bwb03/catalog-cli-pro"
],
"env": {
"CATALOG_API_KEY": "<CATALOG_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e CATALOG_API_KEY=<CATALOG_API_KEY> catalog-cli-pro npx -y @bwb03/catalog-cli-proReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about catalog-cli-pro
How do I install catalog-cli-pro in Claude Code?
Run claude mcp add catalog-cli-pro -e CATALOG_API_KEY=<CATALOG_API_KEY> -- npx -y @bwb03/catalog-cli-pro, replacing the placeholder with your key.
What does catalog-cli-pro do?
It runs 14 checks over an Amazon catalog — attributes, bullets, titles, variation structure. It works as a CLI and as an MCP server for your agent.
What does the server need to run?
A CATALOG_API_KEY environment variable. Seller Central lookups additionally need cookies, supplied locally via --cookie, --cookie-file or CATALOG_SELLER_CENTRAL_COOKIE.
