Pangolinfo MCP - Client Setup Guide

All clients below connect to Pangolinfo MCP via Streamable HTTP — no local install required, just add one URL + API Key to the client’s MCP config.

The examples below use Amazon Insight MCP by default: https://mcp.pangolinfo.com/mcp. For VOC Insight MCP, use https://voc.pangolinfo.com/mcp with the same API Key format.

Streamable HTTP Essentials

Common to all clients:

Amazon Insight MCP URL: https://mcp.pangolinfo.com/mcp
VOC Insight MCP URL: https://voc.pangolinfo.com/mcp
Auth: Header Authorization: Bearer <YOUR_API_KEY>
Protocol: Streamable HTTP (compatible with MCP standard, version auto-negotiated)
API Key: Pangolinfo Console → Profile → API Key (must use Permanent Key)

Below are the config file path + JSON snippet for each client.

Per-Client Config

Claude Code

Config Location

Project-level: project root .mcp.json
User-level: ~/.claude.json (macOS/Linux) or %USERPROFILE%\.claude.json (Windows)

Config Content

{
  "mcpServers": {
    "pangolinfo": {
      "type": "http",
      "url": "https://mcp.pangolinfo.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Restart: /exit then relaunch claude, or open a new session.

Note: Claude Code requires the explicit "type": "http" field to declare remote transport. Without it, the client tries to parse it as stdio and fails.

Cursor

Config Location

Project-level: .cursor/mcp.json in project root
Global: ~/.cursor/mcp.json (macOS/Linux) or %USERPROFILE%\.cursor\mcp.json (Windows)

Config Content

{
  "mcpServers": {
    "pangolinfo": {
      "url": "https://mcp.pangolinfo.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Restart: Click Refresh in the Settings → MCP panel, or restart Cursor.

Note: Cursor doesn’t need an explicit type field — it auto-detects HTTP transport from the url field.

Cline (VS Code Extension)

Config Location

Open the VS Code command palette (Ctrl+Shift+P) and run Cline: Open MCP Settings, which opens:

macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

Config Content

{
  "mcpServers": {
    "pangolinfo": {
      "transportType": "streamableHttp",
      "url": "https://mcp.pangolinfo.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Restart: Click the refresh icon in the top-right of the Cline panel, or reload the VS Code window.

Note: Cline uses transportType instead of type, and the value must be the full string streamableHttp.

Windsurf

Config Location

~/.codeium/windsurf/mcp_config.json (macOS/Linux)
%USERPROFILE%\.codeium\windsurf\mcp_config.json (Windows)

Config Content

{
  "mcpServers": {
    "pangolinfo": {
      "serverUrl": "https://mcp.pangolinfo.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Restart: Click Refresh in Cascade’s MCP settings, or restart Windsurf.

Note: Windsurf uses serverUrl instead of url.

Codex CLI

Config Location

~/.codex/config.toml

Config Content (TOML, not JSON)

[mcp_servers.pangolinfo]
url = "https://mcp.pangolinfo.com/mcp"

[mcp_servers.pangolinfo.headers]
Authorization = "Bearer <YOUR_API_KEY>"

Restart: Exit the codex process and start it again.

Note: Codex uses TOML config. The section name is [mcp_servers.<name>], with headers in a child section.

Hermes

Config Location

Client UI: Settings → Integrations → MCP Servers
Or edit ~/.hermes/mcp.json

Config Content

{
  "servers": {
    "pangolinfo": {
      "url": "https://mcp.pangolinfo.com/mcp",
      "auth": {
        "type": "bearer",
        "token": "<YOUR_API_KEY>"
      }
    }
  }
}

Restart: Click Reload Servers in the MCP settings panel.

Note: Hermes uses the top-level field servers (no mcp prefix) and a structured auth object for credentials.

OpenClaw

Config Location

~/.openclaw/config.json

Config Content

{
  "mcpServers": {
    "pangolinfo": {
      "endpoint": "https://mcp.pangolinfo.com/mcp",
      "apiKey": "<YOUR_API_KEY>"
    }
  }
}

Restart: In the OpenClaw app, select MCP → Reload All Servers from the top menu.

Note: OpenClaw uses endpoint + apiKey field names and auto-constructs the Bearer header on each request.

Common Troubleshooting

Empty tool list → check URL spelling, confirm you’re using a Permanent Key, ensure the client was fully restarted (not just config reload)
401 / auth failed → API Key is invalid or wrong. Regenerate in the console
Timeout → client can’t reach mcp.pangolinfo.com. Check proxy / VPN
Field name errors → field names differ per client (url / serverUrl / endpoint). Copy the snippet for your specific client above

See FAQ for more.

MCP for Agent

Amazon Insight MCP

VOC Insight MCP

​Streamable HTTP Essentials

​Per-Client Config

​Common Troubleshooting

Streamable HTTP Essentials

Per-Client Config

Common Troubleshooting