Add the Vonage MCP server to Claude Desktop

Config last verified Jun 1, 2026

The exact config to run Vonage in Claude Desktop — paste it in, restart, and the tools load.

Prerequisites

Claude Desktop installed.
VONAGE_APPLICATION_ID — Vonage application ID used with the Messages and Voice APIs. Required.
VONAGE_PRIVATE_KEY64 — Base64-encoded private key for your Vonage application. Required.
VONAGE_API_KEY — Vonage account API key. Required.
VONAGE_API_SECRET — Vonage account API secret. Required.

Setup

1. Open `~/Library/Application Support/Claude/claude_desktop_config.json`

On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.

2. Add this configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

{
  "mcpServers": {
    "vonage": {
      "command": "npx",
      "args": [
        "-y",
        "@vonage/vonage-mcp-server-api-bindings"
      ],
      "env": {
        "VONAGE_APPLICATION_ID": "<VONAGE_APPLICATION_ID>",
        "VONAGE_PRIVATE_KEY64": "<VONAGE_PRIVATE_KEY64>",
        "VONAGE_API_KEY": "<VONAGE_API_KEY>",
        "VONAGE_API_SECRET": "<VONAGE_API_SECRET>",
        "VONAGE_VIRTUAL_NUMBER": "<VONAGE_VIRTUAL_NUMBER>",
        "VONAGE_WHATSAPP_NUMBER": "<VONAGE_WHATSAPP_NUMBER>",
        "RCS_SENDER_ID": "<RCS_SENDER_ID>"
      }
    }
  }
}

3. Restart Claude Desktop and confirm the Vonage tools load.

Gotchas

Claude Desktop reads MCP servers from an "mcpServers" object, but the config file is stdio-only: it cannot dial a remote URL directly. To reach a remote server you bridge it locally by running "npx mcp-remote <url>" as the command. Native remote Connectors exist on paid plans, but not through this config file, so the bridge is the portable path.

← Back to the Vonage MCP server