MCP.so
Sign In

Vonage API Bindings MCP Server

@Vonage-Community

About Vonage API Bindings MCP Server

This server integrates a variety of Vonage's APIs as tools to help developers work with their applications.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "vonage-mcp-server-api-bindings": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@vonage/vonage-mcp-server-api-bindings"
      ],
      "env": {
        "VONAGE_APPLICATION_ID": "<YOUR_VONAGE_APPLICATION_ID>",
        "VONAGE_PRIVATE_KEY64": "<YOUR_VONAGE_PRIVATE_KEY64>",
        "VONAGE_API_KEY": "<YOUR_VONAGE_API_KEY>",
        "VONAGE_API_SECRET": "<YOUR_VONAGE_API_SECRET>",
        "VONAGE_VIRTUAL_NUMBER": "<YOUR_VONAGE_VIRTUAL_NUMBER>",
        "VONAGE_WHATSAPP_NUMBER": "<YOUR_VONAGE_WHATSAPP_NUMBER>",
        "RCS_SENDER_ID": "<YOUR_RCS_SENDER_ID>"
      }
    }
  }
}

Tools

15

Get your Vonage Account balance

Send SMS messages with Vonage

Send a text message via WhatsApp using Vonage Messages API

Send a WhatsApp text message with automatic SMS failover using the Vonage Messages API failover feature

Send a text message via RCS using Vonage Messages API

Send an RCS text message with automatic SMS failover using the Vonage Messages API failover feature

Send an outbound voice message with Vonage

List out the applications that are attached to my API key

Create a new Vonage application with a specified name

List of the telephone numbers that are currently associated with my account and their metadata

Search for available phone numbers that can be purchased from Vonage in a specific country

Link an owned number to the assigned Vonage Application

Retrieve a report of activity records from the Vonage Reports API. Supports date-based queries (e.g. "all SMS sent over the last week") and ID-based queries (e.g. "report for Call ID 1234-abcd"). For date-based queries provide product, direction (required for SMS/MESSAGES), and optionally date_start/date_end. For ID-based queries provide product and id (comma-separated UUIDs, max 20).

Generates an interactive Chart.js chart from data.

INTERNAL SYSTEM TOOL. DO NOT CALL. This tool is strictly for the frontend UI iframe to execute native filesystem saves. You (the AI model) do not have access to the base64 canvas data required to use this tool. Any attempt by the AI to call this tool will fail. Ignore this tool entirely.

Overview

What is Vonage API Bindings MCP Server?

The Vonage API Bindings MCP Server is a Model Context Protocol server that provides access to various Vonage API functionalities through a set of predefined tools. It is designed for developers using MCP-compatible clients (such as VS Code, Cursor, Windsurf, or Claude Desktop) to interact with Vonage services via natural language prompts.

How to use Vonage API Bindings MCP Server?

Configure the server in your MCP client by adding a JSON entry with "type": "stdio", "command": "npx", "args": ["-y", "@vonage/vonage-mcp-server-api-bindings"], and set required environment variables (VONAGE_APPLICATION_ID, VONAGE_PRIVATE_KEY64, VONAGE_API_KEY, VONAGE_API_SECRET, VONAGE_VIRTUAL_NUMBER, VONAGE_WHATSAPP_NUMBER, RCS_SENDER_ID). Then invoke tools using natural language prompts such as “Can you check my Vonage account balance?”.

Key features of Vonage API Bindings MCP Server

  • Check Vonage account balance
  • List, create, and link Vonage applications
  • List and link purchased telephone numbers
  • Send SMS messages via Vonage
  • Send WhatsApp messages with optional SMS failover
  • Send RCS messages with optional SMS failover
  • Send outbound voice messages

Use cases of Vonage API Bindings MCP Server

  • Query your Vonage account balance from an MCP client
  • List and manage applications attached to your API key
  • Send an SMS, WhatsApp, RCS, or voice message to a phone number
  • Send a WhatsApp or RCS message with automatic SMS fallback

FAQ from Vonage API Bindings MCP Server

Which environment variables must I set?

You must set VONAGE_API_KEY, VONAGE_API_SECRET, VONAGE_APPLICATION_ID, VONAGE_PRIVATE_KEY64, VONAGE_VIRTUAL_NUMBER, VONAGE_WHATSAPP_NUMBER, and RCS_SENDER_ID.

How do I get the base64-encoded private key?

The README points to a browser-based tool at https://mylight.work/private-key-to-environment-variable that converts your private key file into the base64 string. No data is sent outside your browser.

What MCP clients are supported?

The README provides setup links for VS Code, Cursor, Windsurf, and Claude Desktop.

What transport does the server use?

The server uses stdio transport, configured as "type": "stdio" in the MCP client.

Can I use the server without a Vonage application ID?

No. The VONAGE_APPLICATION_ID is listed as a required environment variable.

Frequently asked questions

Which environment variables must I set?

You must set `VONAGE_API_KEY`, `VONAGE_API_SECRET`, `VONAGE_APPLICATION_ID`, `VONAGE_PRIVATE_KEY64`, `VONAGE_VIRTUAL_NUMBER`, `VONAGE_WHATSAPP_NUMBER`, and `RCS_SENDER_ID`.

How do I get the base64-encoded private key?

The README points to a browser-based tool at `https://mylight.work/private-key-to-environment-variable` that converts your private key file into the base64 string. No data is sent outside your browser.

What MCP clients are supported?

The README provides setup links for VS Code, Cursor, Windsurf, and Claude Desktop.

What transport does the server use?

The server uses stdio transport, configured as `"type": "stdio"` in the MCP client.

Can I use the server without a Vonage application ID?

No. The `VONAGE_APPLICATION_ID` is listed as a required environment variable.

Comments

More Developer Tools MCP servers