Voc Amazon Reviews

Created By
Hunter Guo18 days ago
Agent-native Amazon review intelligence — fetches verified reviews from 10 marketplaces via real Shulex OpenAPI (not scrapers) and produces copy-ready listing improvements grounded in actual customer language. Backed by a 2B-review historical dataset that Helium 10 / Jungle Scout can't replicate. Works in any MCP client (Claude Code, Claude Desktop, ChatGPT, Cursor, Windsurf, VS Code, Cline).
Overview

VOC Amazon Reviews — Agent-Native Review Intelligence

Fetch and analyze verified Amazon reviews from 10 marketplaces (US, CA, MX, GB, DE, FR, IT, ES, JP, AU) via real Shulex OpenAPI — not scrapers. Built for AI agents running Amazon-seller workflows.

What it does

ToolWhat it does
fetch_reviewsPull verified Amazon reviews for any ASIN, up to 1000 per call
analyze_reviewsTurn raw reviews into structured VOC reports (themes, sentiment, complaints)
voc_fullOne-shot fetch + analyze for ad-hoc seller questions
extract_listing_improvementsGenerate copy-ready title, 5 bullets, description — grounded in real customer language. Uses Claude Opus 4.7 + proprietary rubric distilled from Shulex's 2B-review corpus
analyze_csvRun VOC analysis on any CSV/Excel (Walmart, Shopify, support tickets)
render_dashboardGenerate standalone HTML dashboards

Why it's different

  • Real OpenAPI access, not DOM scraping — won't break when Amazon changes HTML
  • Verified-purchase, Vine, helpful-vote, variant signals included in every review
  • Proprietary listing rubric trained on 2B+ historical Amazon reviews (data indexed before Amazon's access restrictions; cannot be replicated by buying API access today)
  • Agent-first design — tool schemas, error codes, and metadata optimized for LLM router selection

Installation (one line)

Add this to your MCP client config (Claude Code, Cursor, Cline):

{
  "mcpServers": {
    "voc-amazon-reviews": {
      "command": "uvx",
      "args": [
        "voc-amazon-reviews-mcp"
      ],
      "env": {
        "VOC_API_KEY": "your-shulex-key",
        "ANTHROPIC_API_KEY": "your-anthropic-key"
      }
    }
  }
}

Requires uv (install). First run pulls the repo and resolves deps in ~10s; subsequent runs are instant.

Get a free Shulex API key (100 calls/month, no credit card): apps.voc.ai/openapi

Example workflows

Listing rewrite: "Pull reviews of my ASIN and the top 3 competitors. Rewrite my listing to attack their weak points." → agent calls fetch_reviews × 4 → analyze_reviews × 4 → extract_listing_improvements → complete listing draft.

Daily monitoring: Schedule voc_full × 10 ASINs daily via cron; alerts on new negative theme clusters.

Competitor gap analysis: "What do customers complain about in this category that no top seller addresses?" → fetch_reviews × 5 → analyze_reviews → list of unaddressed pain points.

License

MIT

Server Config

{
  "mcpServers": {
    "voc-amazon-reviews": {
      "command": "uvx",
      "args": [
        "voc-amazon-reviews-mcp"
      ],
      "env": {
        "VOC_API_KEY": "your-shulex-key",
        "ANTHROPIC_API_KEY": "your-anthropic-key"
      }
    }
  }
}
Project Info
Created At
18 days ago
Updated At
17 days ago
Author Name
Hunter Guo
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Payai X402 Tools

20 hours ago
Meteomatics

16 hours ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

3 hours ago
Voyei

a day ago