Vonage API Bindings MCP Server

Created By
Vonage-Community6 months ago
This server integrates a variety of Vonage's APIs as tools to help developers work with their applications.
Overview

What is Vonage API Bindings MCP Server?

The Vonage API Bindings MCP Server integrates various Vonage APIs to assist developers in managing their applications effectively.

How to use Vonage API Bindings MCP Server?

To use the MCP server, set up the environment variables with your Vonage credentials and run the server using the provided command. You can then access various API functionalities through simple commands.

Key features of Vonage API Bindings MCP Server?

  • Access to account management tools (e.g., check balance, list applications)
  • Messaging capabilities (e.g., send SMS, WhatsApp, RCS messages)
  • Voice message sending functionality
  • Easy integration with existing applications

Use cases of Vonage API Bindings MCP Server?

  1. Managing Vonage account settings and applications.
  2. Sending SMS and WhatsApp messages for notifications or alerts.
  3. Implementing voice messaging features in applications.
  4. Utilizing RCS for enhanced messaging experiences.

FAQ from Vonage API Bindings MCP Server?

  • What APIs are available through this server?

The server provides access to account management, messaging, and voice APIs.

  • Is there a cost associated with using Vonage APIs?

Yes, usage of Vonage APIs may incur costs based on the services used.

  • How do I set up the server?

Follow the setup instructions provided in the documentation, including setting environment variables and running the server command.

Server Config

{
  "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>"
      }
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
Vonage-Community
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago