# VOC OpenAPI MCP [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/SolveaCX/voc-mcp  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/voc-openapi-mcp

## Description
Analyze authorized Amazon reviews and feedback for VOC insights, tagging, and listing optimization.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "voc-openapi-mcp": {
    "command": "npx",
    "args": ["-y","voc-openapi-mcp@latest"],
    "env": {
      "VOC_OPENAPI_API_KEY": "",
      "VOC_API_KEY": "",
      "X_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `VOC_OPENAPI_API_KEY`, `VOC_API_KEY`, `X_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the VOC OpenAPI MCP MCP server does

The VOC OpenAPI MCP MCP server gives AI clients access to VOC's Amazon review and feedback capabilities through the Model Context Protocol. It is intended for e-commerce operators, product researchers, consumer-insights teams, and agents working with authorized VOC account data.

The available workflows cover current and historical Amazon review retrieval, sentiment analysis, customer pain points, recurring themes, listing improvement suggestions, and structured tagging. Feedback and product listings can be organized into taxonomies for repeatable analysis. The repository describes seven curated tools for catalog inspection and evaluation, while the hosted endpoint exposes the published VOC OpenAPI tool set.

## How it works

The hosted MCP endpoint is `https://open.voc.ai/mcp-server`, and the configured server name is `voc-openapi`. Requests use the `X-API-Key` authentication header. Browser authorization is the default flow: the installer opens VOC's authorization page, waits for sign-in and approval, and then configures detected clients. If a browser cannot open, it prints the authorization URL for manual use.

An API key can be supplied instead through the setup command or the `VOC_OPENAPI_API_KEY` environment variable. The service receives the selected tool inputs and the credential needed for the authorized VOC account. Review the project's privacy and security documentation before sending production data.

## Setup and configuration

The VOC OpenAPI MCP MCP server provides shell and PowerShell installers, as well as an npm setup command. The shell installer is available at `https://open.voc.ai/install.sh`; the PowerShell version is available at `https://open.voc.ai/install.ps1`. The npm setup command is `npx voc-openapi-mcp@latest setup`.

By default, setup detects supported clients and updates their MCP configuration in place. Supported clients listed by the project include Claude Code, Claude Desktop, Cursor, Windsurf, WorkBuddy, Gemini CLI, and Codex. Configuration locations vary by client; examples include `~/.cursor/mcp.json`, `~/.codeium/windsurf/mcp_config.json`, `~/.claude.json`, and `~/.codex/config.toml`. The installer does not create backup files.

Codex users can add the optional VOC OpenAPI query skill with `setup --with-skill`. A dry-run mode is available for previewing configuration changes. The installer can also register every supported agent with `--all-agents`.

## Tools and capabilities

The VOC OpenAPI MCP MCP server supports these documented capability areas:

- Fetch current or historical Amazon reviews.
- Analyze sentiment, pain points, and themes.
- Generate listing improvements from customer feedback.
- Tag feedback and product listings using structured taxonomies.
- Expose seven curated tools through `tools/list` in local stdio mode.
- Provide access to the full published VOC OpenAPI tool set through the hosted endpoint.

The local `serve` mode is intended for catalog scanners and Docker-based evaluation. It exposes the curated tools for introspection, but actual tool calls require an API key and return an explicit credential error when none is supplied. Production users are directed to the hosted VOC endpoint rather than the local evaluation mode.

## Limitations and notes

Access is limited to authorized VOC account data and requires browser authorization or an API key for real requests. The installer currently stores an API key as plain text in the local MCP client configuration when that authentication method is used. Keep the key out of source control, logs, screenshots, issues, and chat messages.

The repository's installer code is licensed under Apache License 2.0. The hosted VOC service and its business functions are governed separately by VOC's terms and conditions. The material does not state a service price or free-tier policy, so pricing should be confirmed with VOC.

_Full upstream README: https://allmcps.com/mcp/voc-openapi-mcp/readme_