vonage-mcp-server-api-bindings

Vonage Server API Bindings MCP Server

Vonage API bindings expose account, phone-number, messaging, and reporting operations through MCP tools. Developers can inspect applications, connect owned numbers, send messages across supported channels, and chart data.

Server facts

vonage-mcp-server-api-bindings

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
3
Last commit
Data as of

Tags

  • communications
  • cpaas
  • sms
  • voice
  • vonage

Overview

Vonage account and communications workflows come together in this MCP integration for developers working with Vonage applications. Account tools retrieve balances, inspect applications associated with an API key, and create named applications. Number tools show owned telephone numbers with their metadata, search for numbers available to purchase in a chosen country, and associate an owned number with an application. These operations cover both reviewing existing account resources and setting up application-to-number relationships without implying that the number-search tool also completes purchases.

Communication tools support SMS, WhatsApp text, RCS text, and outbound voice messages. WhatsApp and RCS each have a separate sending option that uses SMS as an automatic fallback. For activity review, the Reports API tool accepts queries organized by dates or record identifiers, allowing requests focused on a period of activity or particular records. A charting tool produces interactive Chart.js visualizations from data. The server uses stdio transport, and the setup material includes configurations for VS Code, Cursor, Windsurf, and Claude Desktop.

vonage-mcp-server-api-bindings setup notes

  • vonage-mcp-server-api-bindings records stdio only; confirm a network transport upstream before planning remote access.
  • vonage-mcp-server-api-bindings has no recorded license; confirm reuse terms in its repository.

Related MCP servers