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.

Basic information

Category

Developer Tools

Transports

stdio

Publisher

Vonage-Community

Submitted by

Chris Tankersley

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

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

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.

Comments

More Developer Tools MCP servers