Add the Vonage MCP server to Cursor

Prerequisites

• Cursor 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

{
  "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>"
      }
    }
  }
}

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.