Wapix MCP

Quick start

  1. 1Open Admin → MCP Access.
  2. 2Select the tenant.
  3. 3Select Cloud sessions or leave all Cloud sessions allowed.
  4. 4Choose a preset (READ ONLY / OPERATIONS / FULL). Destructive is a separate checkbox.
  5. 5Copy the token once (wpx_mcp_…).
  6. 6Point the client at https://wapix.cloud/mcp

Cursor YES

Cursor’s official mcp.json schema includes headers.Authorization. The token does not have to be plaintext in mcp.json; use ${env:WAPIX_MCP_ACCESS_TOKEN}.

{
  "mcpServers": {
    "wapix-whatsapp": {
      "url": "https://wapix.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ${env:WAPIX_MCP_ACCESS_TOKEN}"
      }
    }
  }
}

Local stdio (verified; not hosted Bearer):

{
  "mcpServers": {
    "wapix-whatsapp": {
      "command": "npm",
      "args": ["run", "mcp:whatsapp"],
      "env": { "WAPIX_MCP_ACCESS_TOKEN": "<grant token>" }
    }
  }
}

Claude Code YES

Official Claude Code HTTP MCP: type:"http" plus headers.Authorization (or claude mcp add --header). The token can live in an environment variable.

{
  "mcpServers": {
    "wapix-whatsapp": {
      "type": "http",
      "url": "https://wapix.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ${WAPIX_MCP_ACCESS_TOKEN}"
      }
    }
  }
}
claude mcp add --transport http wapix-whatsapp https://wapix.cloud/mcp \
  --header "Authorization: Bearer <grant token>"

Claude Desktop NO

Claude Desktop does not support native remote HTTP with a custom Bearer header. There is no invented hosted config. Use local stdio and WAPIX_MCP_ACCESS_TOKEN.

{
  "mcpServers": {
    "wapix-whatsapp": {
      "command": "npm",
      "args": ["run", "mcp:whatsapp"],
      "env": { "WAPIX_MCP_ACCESS_TOKEN": "<grant token>" }
    }
  }
}

ChatGPT NO

ChatGPT custom Authorization: Bearer is not verified. There is no working hosted config.