vonage -api-bindings
Vonage MCP server with tools to interact with APIs
claude mcp add --transport stdio vonage-community-vonage-mcp-server-api-bindings npx -y @vonage/vonage-mcp-server-api-bindings \ --env RCS_SENDER_ID="YOUR_RCS_SENDER_ID" \ --env VONAGE_API_KEY="YOUR_VONAGE_API_KEY" \ --env VONAGE_API_SECRET="YOUR_VONAGE_API_SECRET" \ --env VONAGE_PRIVATE_KEY64="BASE64_ENCODED_PRIVATE_KEY" \ --env VONAGE_APPLICATION_ID="YOUR_VONAGE_APPLICATION_ID" \ --env VONAGE_VIRTUAL_NUMBER="YOUR_VONAGE_VIRTUAL_NUMBER" \ --env VONAGE_WHATSAPP_NUMBER="YOUR_VONAGE_WHATSAPP_NUMBER"
How to use
This MCP server exposes a variety of Vonage API capabilities as MCP tools. Categories include Account Management (balance, list/create applications, list purchased numbers), Number Management (search available numbers, link numbers to applications), Reports (retrieve activity records), and Messaging & Communication (SMS, WhatsApp, RCS, and outbound voice messages). Each tool corresponds to a Vonage API action, enabling you to programmatically query balances, manage Vonage applications and numbers, generate reports, and send messages across SMS, WhatsApp, and RCS channels. To use these tools, send natural-language prompts that map to the tool names, e.g., asking to check your balance, search for numbers, or send an SMS. The MCP server will interpret your request and execute the appropriate Vonage API call behind the scenes. The provided usage examples in the README illustrate conversational prompts for performing common tasks such as listing applications, creating an application, searching numbers, and sending messages across channels.
How to install
Prerequisites:
- Node.js (version 14 or newer) and npm installed on your system
- Access to run MCP servers using your preferred MCP runtime (VS Code MCP extension, Cursor, Windsurf, or Claude Desktop)
Installation steps:
-
Ensure Node.js and npm are installed. Verify with: node -v npm -v
-
Install or run the MCP server package via npx (as configured): npx -y @vonage/vonage-mcp-server-api-bindings
-
Alternatively, you can install the package locally in a project: npm install @vonage/vonage-mcp-server-api-bindings
-
Prepare your environment variables (see mcp_config example) and then run the MCP server using your preferred MCP runner (VS Code, Cursor, Windsurf, or Claude Desktop). The example configuration in the README demonstrates the required environment variables and how to wire them into the runtime.
-
Verify the server loads and is responsive by issuing a simple prompt like: "Check account balance"
Additional notes
Notes and tips:
- The environment variables are required for authenticating with Vonage services. Ensure your keys and IDs are kept secure.
- The private key is accepted in base64-encoded form (VONAGE_PRIVATE_KEY64). If you use a different encoding, adjust accordingly in the env config.
- If you encounter connection or authentication errors, double-check that all API keys, secrets, and numbers are correctly configured and that your Vonage account has the necessary permissions.
- The MCP server supports concurrency through the standard MCP runtime. If you plan to run multiple Vonage actions, consider rate limits on the Vonage API endpoints.
- For troubleshooting, refer to the provided usage examples in the README and experiment with conversational prompts to ensure the server correctly maps prompts to tools.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.