
VOC Amazon Reviews
io.github.mguozhenPublished by GitHub account mguozhenv0.1.1Updated Nov 3, 2026
Amazon review intelligence via Shulex OpenAPI. 10 marketplaces, verified-purchase & Vine signals.
Overview
Amazon review intelligence server that fetches reviews by ASIN or CSV and returns sentiment, pain points, listing copy and an HTML dashboard.
- What you can do
- Fetch raw Amazon reviews for an ASIN across 10 marketplaces, or load your own review CSV/Excel with fuzzy column detection
- Analyze reviews into a voice-of-customer report with sentiment, pain points and structured JSON or Markdown output
- Run a one-call full VOC report that fetches and analyzes in a single step
- Generate copy-ready listing improvements (title, bullets, description) grounded in customer language
- Render a standalone HTML dashboard from a VOC report
- When to use it
- Useful for Amazon sellers, e-commerce analysts and copywriters who want an assistant to turn reviews into sentiment summaries, pain points and listing copy without manual exports. Also fits non-Amazon products when you already have a review file to analyze.
- Requirements
- Runs locally as a Python package via uvx (uv required), or as a hosted/HTTP deployment. Requires a Shulex VOC OpenAPI key in VOC_API_KEY; the optional ANTHROPIC_API_KEY is needed only for the listing-improvements tool and must be a real Anthropic key. Network access to the Shulex API.
Installation
In SourceWeft
- Open VOC Amazon Reviews in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Review Analyzer
Agent-native voice-of-customer for e-commerce.
Drop in an ASIN or a CSV — get sentiment, pain points, copy-ready listing improvements,
and a black-gold HTML dashboard. 6 MCP tools. Backed by the most stable Amazon review data layer.
[30s Setup] [6 MCP tools] [10 Markets] [Cline] [awesome-mcp-servers] [MIT]
↑ Sample dashboard: B08N5WRWNW · 100 reviews · sentiment + pain points + listing improvements, generated by render_dashboard.
TL;DR
Two inputs, six tools, three outputs.
- Inputs — Amazon ASIN (auto-fetched via Shulex VOC OpenAPI, 10 markets) or any review CSV / Excel (Helium 10 / eBay / Shopify / custom — fuzzy column detection)
- Outputs — Markdown report · structured JSON · standalone HTML dashboard
- Surface — MCP server (works in Claude Code / Cursor / Cline / Continue) and Skill (works in Claude Code)
Quick start
Option A — As an MCP server (recommended)
Requires uv.
Add this to your MCP client config (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code Copilot, Cline, Continue.dev):
Get a free Shulex API key (100 calls/month, no credit card): apps.voc.ai/openapi.
Optional: Add "ANTHROPIC_API_KEY": "sk-ant-..." to enable extract_listing_improvements (the only tool that calls Claude directly — others work without it). Must be an actual Anthropic key; other providers won't work.
First run resolves dependencies in ~5s; subsequent runs are instant.
Try it
Ask any MCP-compatible agent:
Run a VOC report on
B08N5WRWNW, render the dashboard, and write it to~/Desktop/voc.html.
The agent will call voc_full → render_dashboard and hand you the file.
Option B — One-shot CLI
Option C — Bring your own reviews (CSV)
Option D — Hosted on Smithery (no install)
Connect to the server remotely — no uvx, no Python, no local install. Bring
your own Shulex API key (Smithery prompts for it on first connection).
This repo ships a Dockerfile and smithery.yaml for one-click deploy.
To run your own hosted instance:
- Fork or clone this repo to your GitHub.
- Sign in at smithery.ai with GitHub.
- Deploy a server → pick the repo. Smithery builds the container and exposes an HTTPS MCP endpoint.
- Share the URL with users; they paste it into Claude / Cursor / Cline.
The same image runs anywhere that takes a Dockerfile — Fly.io, Railway, Cloudflare Workers (with adapter), Render, Cloud Run.
To run the HTTP transport locally (e.g. for testing):
Option E — Deploy to Vercel (serverless)
This repo also ships vercel.json + app.py for one-click Vercel
deploys. Sign in at vercel.com with GitHub, import the
repo, and Vercel auto-detects the Python function.
Set these in Project Settings → Environment Variables before the first deploy:
Timeout caveat: Vercel functions cap at 10s (Hobby default), 60s
(Hobby with maxDuration: 60 — already set in vercel.json), or 300s
(Pro). Long-running tools like voc_full (30-90s) and
extract_listing_improvements (20-60s) may exceed these limits. For
unbounded execution, prefer Option D (Docker/Render/Fly) or local install.
The MCP endpoint after deploy: https://your-project.vercel.app/mcp
Tools
All 6 tools speak MCP. All return JSON-serializable dicts. Full schemas in mcp_server/README.md.
Data layer — why this is the moat
Most "AI review tools" are a thin LLM wrapper over a brittle scraper. We invert that. The data layer is the moat:
For non-Amazon platforms, analyze_csv accepts any review file — fuzzy column matching detects 内容 / 评价 / body / review / content so you don't have to reformat. Bring data from anywhere, get the same VOC report.
vs. the alternatives
Credit & inspiration: The 22-dimension tag system, fuzzy CSV column detection, and black-gold dashboard aesthetic were inspired by buluslan/review-analyzer-skill (MIT). We adapted them onto an MCP-native architecture with the Shulex VOC OpenAPI data layer.
Architecture
- fetch + analyze loop: shell scripts (proven, reproducible, easy to debug)
- listing rewrites: Anthropic SDK direct (
claude-opus-4-7+ adaptive thinking + prompt caching on the system rubric) - dashboard: pure stdlib HTML rendering, no node / no react
Distribution / where to find us
Roadmap
- Drop in CSV / Excel (any platform, fuzzy column detect)
- 22-dimension tag system (YAML-configurable)
- Black-gold HTML dashboard tool
- 6 MCP tools shipped
-
npx skills add mguozhen/review-analyzerone-line install - CLI subprocess engine option (use your Claude subscription, $0 API)
- PyPI publish + official MCP Registry submission
- Smithery deploy config (
smithery.yaml+Dockerfile) - Vercel deploy config (
vercel.json+app.py) - Smithery / mcp.so / PulseMCP form submissions
License
MIT. See LICENSE.
Acknowledgments: Tag schema, CSV column detection, and dashboard visual design inspired by buluslan/review-analyzer-skill. Data layer powered by Shulex VOC OpenAPI.
Source: README.md at commit 31b2c4b
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.