Vonage MCP Server Update: Reports, Numbers, and Charts

The Vonage MCP Server API Bindings let AI assistants use Vonage APIs through the Model Context Protocol (MCP). Since December 2025, versions 1.3.0 through 1.5.1 have shipped three releases worth of new functionality. We’ve added reporting, number management, application creation, and chart generation.

You can now pull Reports API data, search for and provision phone numbers, create applications, and turn report data into charts, all from inside your AI assistant. This post walks through what's new since December 2025.

If you haven't set up the server yet, see our earlier post, Step-by-Step: Adding Vonage APIs to Your AI Agent with MCP, for the basics.

Why These Updates Matter

These additions let you complete more Vonage workflows without switching between your AI assistant, the Vonage API Dashboard, and custom scripts. You can now inspect communication activity, find and configure numbers, create applications, and visualize report data in one conversation.

Application Creation

Version 1.3.0 added a create-application tool, so you can spin up a new Vonage application by name without leaving your chat window:

Can you create a new Vonage application called "My Chat App"?

Or, if you don't care about the name, just ask the assistant to create one and let it suggest something.

Reports API Access

Version 1.4.0 introduced get-records-report, which pulls activity records from the Reports API. You can query by date range or by a specific record ID:

Can you get a report of all outbound SMS sent over the last week?

Can you get the report for Voice Call ID 1234-abcd-5678-efgh?

If you want to see get-records-report powering a full interactive UI, check out Build a Reports Dashboard in Claude Desktop with MCP Apps and Vonage. It covers building a live SMS and voice report dashboard that renders directly inside Claude.

Number Search and Provisioning Number Search and Provisioning

Also in 1.4.0, two new tools round out number management:

• search-available-numbers — search for purchasable numbers by country, with optional filters for capabilities (SMS, VOICE) or a number pattern

• link-number-to-vonage-application — attach a number you own to a specific Vonage application

Combined with the existing list-purchased-numbers tool, you can go from "what do I own" to "what's available" to "attach this number to my app" in one conversation:

Can you search for available Vonage numbers in the US with SMS and VOICE features?

Can you search for available numbers in GB starting with pattern "44207*"?

Chart Generation

Version 1.5.0 added make-chart, which takes data you've already retrieved, like a Reports API query, and renders it as a chart:

Please create a chart showing all the outbound SMS sent over the last week.

The make-chart tool was contributed by a first-time contributor, a good sign for an open-source project, and a good reminder that the repo accepts PRs. Check out how to contribute to the Open Source Vonage MCP Tooling Server.

Reliability and Housekeeping

The 1.5.0 and 1.5.1 releases also included a handful of fixes worth knowing about:

• WhatsApp failover fix: whatsapp-send-text was incorrectly triggering SMS failover. That's fixed — failover is still available explicitly through whatsapp-send-text-with-sms.

• Error handling: list-applications and list-purchased-numbers now handle and surface errors properly instead of failing silently.

• Custom user agent: outbound requests from the server now carry a distinct user agent, so MCP-driven traffic is identifiable in our logs separate from other API traffic.

• Dependency bump: @vonage/server-sdk updated to v3.26.0.

• Broken import fix: 1.5.1 patched a broken import that shipped in 1.5.0. If you're on 1.5.0, update to 1.5.1.

Get Started Today

Update your MCP configuration to pull the latest version:

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

Since the config runs through npx, restarting your MCP client is all it takes to pick up the latest release.

Conclusion