VOC OpenAPI MCP

io.github.SolveaCXPublished by GitHub account SolveaCXv1.0.5Updated Oct 24, 2026

VOC OpenAPI gives AI agents authorized review and product data for insights, tagging, and listings.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

VOC OpenAPI MCP gives an AI assistant authorized Amazon review and product data for insights, feedback tagging, and listing optimization.

What you can do
Fetch current or historical Amazon reviews for products and listings, with sentiment, pain-point and theme analysis on top of them. Generate listing improvement suggestions from customer feedback. Tag reviews and product listings into structured taxonomies. Run the published VOC OpenAPI data tools through the hosted endpoint, combining product, listing, review and competitive-positioning data in one request.
When to use it
Useful for e-commerce operators, consumer-insights teams and product researchers who want an assistant to pull authorized Amazon review data and turn it into VOC analysis, tagging or listing optimization suggestions.
Requirements
A remote MCP endpoint at open.voc.ai, reached over streamable HTTP. A VOC account with an API key sent in the X-API-Key header, obtained by browser sign-in or supplied directly. The optional installer is an npm package and writes MCP configuration for detected clients such as Claude, Cursor, Codex and Gemini CLI.
Before you install
The X-API-Key is stored as plain text in the local MCP client configuration file, so keep it private and out of commits, logs and screenshots. Some tools create tasks and consume credits. The hosted server receives the selected tool inputs and the API key. The installer modifies existing client configuration in place without creating backup files.

Installation

In SourceWeft

  1. Open VOC OpenAPI MCP in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.SolveaCX%2Fvoc-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "voc-openapi": {
      "type": "http",
      "url": "https://open.voc.ai/mcp/catalog",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

VOC OpenAPI MCP Installer

English | 简体中文

Install the full VOC OpenAPI MCP server for Amazon review insights, feedback tagging, listing optimization, and hundreds of published data tools in local AI clients.

Built for e-commerce operators, consumer-insights teams, product researchers, and AI agents that need authorized review data and repeatable VOC workflows.

Usage

bash
curl -fsSL https://open.voc.ai/install.sh | bash

By default, the installer opens your browser to sign in to VOC and approve access. After authorization, it automatically writes the MCP configuration for the supported clients detected on your machine, including Codex, Claude, Cursor, and others listed below.

Windows PowerShell:

powershell
irm https://open.voc.ai/install.ps1 | iex

Alternatively, use the npm package directly:

bash
npx voc-openapi-mcp@latest setup

Codex users can also install the general-purpose VOC OpenAPI query skill:

bash
npx voc-openapi-mcp@latest setup --with-skill

The skill is written to ~/.agents/skills/voc-openapi/SKILL.md only when Codex is detected. The uninstaller removes only installer-managed versions that have not been modified by the user.

By default, the installer registers the agents detected on the local machine. It currently supports:

  • Claude Code (CLI; writes to ~/.claude.json)
  • Claude Desktop (desktop app; detects the macOS app or Windows %LOCALAPPDATA%\AnthropicClaude, writes to claude_desktop_config.json, and bridges the remote MCP server through mcp-remote)
  • Cursor (desktop app or CLI launcher; detects the macOS app or Windows %LOCALAPPDATA%\Programs\cursor, both using ~/.cursor/mcp.json)
  • Windsurf (desktop app or CLI launcher; detects the macOS app or Windows %LOCALAPPDATA%\Programs\Windsurf, both using ~/.codeium/windsurf/mcp_config.json)
  • WorkBuddy (desktop app; writes user-level ~/.workbuddy/mcp.json)
  • Gemini CLI (writes to ~/.gemini/settings.json)
  • Codex (CLI and Desktop both use ~/.codex/config.toml)

List the agents detected on the local machine:

bash
curl -fsSL https://open.voc.ai/install.sh | bash -s -- --list-agents

Windows PowerShell:

powershell
& ([scriptblock]::Create((irm https://open.voc.ai/install.ps1))) -ListAgents

Register every supported agent (the installer detects installed clients automatically by default, so this is usually unnecessary):

bash
npx voc-openapi-mcp@latest setup --all-agents

Default configuration:

  • Codex: $CODEX_HOME/config.toml, or ~/.codex/config.toml when CODEX_HOME is not set
  • Claude Code: ~/.claude.json
  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (or %APPDATA%\Claude\claude_desktop_config.json on Windows)
  • Cursor: ~/.cursor/mcp.json
  • Windsurf: ~/.codeium/windsurf/mcp_config.json
  • WorkBuddy: ~/.workbuddy/mcp.json
  • Gemini CLI: ~/.gemini/settings.json
  • MCP server name: voc-openapi
  • MCP URL: https://open.voc.ai/mcp-server
  • Authentication header: X-API-Key
  • Full endpoint: all published VOC OpenAPI MCP tools
  • Codex MCP startup timeout: 120 seconds

The installer updates the corresponding MCP server configuration in place and does not create .bak backup files.

Options

bash
voc-mcp setup \  --api-base https://open.voc.ai \  --name voc-openapi \  --with-skill \  --config ~/.codex/config.toml

Authentication

Browser sign-in is the default and recommended flow. The installer opens the VOC authorization page in your default browser, waits for you to sign in and approve access, then updates the detected AI clients automatically. If the browser cannot be opened, the installer prints the same authorization URL so you can open it manually. You do not need to copy a credential from the browser back into the terminal.

API Key alternative

You can also skip browser authorization and provide an API key directly:

bash
VOC_OPENAPI_API_KEY=voc_live_sk_xxx npx voc-openapi-mcp@latest setup

Keep the API key private: do not commit it, paste it into issues or chat, or include it in screenshots and logs. Prefer the environment variable above over putting the key directly in a shared command or script.

Preview

bash
npx voc-openapi-mcp@latest setup --api-key voc_live_sk_xxx --dry-run

Note: To support a one-command setup, the API key is currently stored as plain text in the local MCP client configuration file.

Local stdio server for catalog scanners

Catalog scanners such as Glama primarily use the repository Dockerfile to build and start a minimal local stdio MCP server for evaluation. From a source clone or Docker image, the server command is:

bash
node bin/voc-mcp.js serve

After the npm package release, the equivalent package command is:

bash
npx voc-openapi-mcp@latest serve

This mode exposes the same seven curated tools through tools/list for catalog introspection and Docker-based evaluation. Real tools/call requests require VOC_OPENAPI_API_KEY, VOC_API_KEY, or X_API_KEY; without a key the server returns an explicit API-key-required error instead of fake business results. Production users should continue to use the hosted endpoint https://open.voc.ai/mcp/catalog.

Example result

[VOC OpenAPI MCP product analysis result covering listing data, review insights, pain points, competitive positioning, and recommended actions]

This single agent request combines product and listing data, review insights, customer pain points, competitive positioning, and recommended actions. Click the image to view the full result.

Capabilities

  • Fetch current or historical Amazon reviews.
  • Analyze sentiment, pain points, and themes.
  • Generate listing improvements from customer feedback.
  • Tag feedback and product listings into structured taxonomies.

See TOOLS.md for all seven tools, input fields, credit costs, and task-creating side effects.

Privacy, permissions, and support

The hosted server only receives the selected tool inputs and the X-API-Key required for the authorized VOC account. The installer writes only the selected AI client's MCP configuration and the optional VOC skill. Review PRIVACY.md and SECURITY.md before installation.

License

The installer source code is licensed under the Apache License 2.0. The hosted VOC OpenAPI service and its business capabilities remain subject to the VOC Terms and Conditions.

Source: README.md at commit 135f87a

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.5LatestSep 16, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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