Voc MCP Server

Install the full VOC OpenAPI MCP server in Claude, Codex, Cursor, and other AI clients.

Remote serverstreamable-http

What is the Voc MCP server?

Install the full VOC OpenAPI MCP server in Claude, Codex, Cursor, and other AI clients. That is what the voc mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

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.

  • 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

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Codex — $CODEX_HOME/config.toml, or ~/.codex/config.toml when CODEX_HOME is not set
  • Cursor — ~/.cursor/mcp.json
  • Windsurf — ~/.codeium/windsurf/mcp_config.json
  • WorkBuddy — ~/.workbuddy/mcp.json

What it needs from you

Configuration is passed through the environment: VOC_OPENAPI_API_KEY, VOC_API_KEY, X_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Voc's toolset — Codex, Cursor, Windsurf and 1 more — is a fair guide to whether it matches your workflow. It is maintained by swing.hu; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
Codex$CODEX_HOME/config.toml, or ~/.codex/config.toml when CODEX_HOME is not set
Cursor~/.cursor/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
WorkBuddy~/.workbuddy/mcp.json

How to install the Voc MCP server

{
  "mcpServers": {
    "openapi-1": {
      "command": "npx",
      "args": ["-y", "voc-openapi-mcp"],
      "env": {
        "VOC_OPENAPI_API_KEY": "your-value",
        "VOC_API_KEY": "your-value",
        "X_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
VOC_OPENAPI_API_KEYCredential the server authenticates with.Yes
VOC_API_KEYCredential the server authenticates with.Yes
X_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Voc to Codex.
  • Use Voc to Cursor.
  • Use Voc to Windsurf.

Frequently asked questions

It connects Voc to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Codex, Cursor, Windsurf, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Voc directly.