Vonage Documentation MCP Server
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport streamable-http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
vonage_docs_search— Searches the official Vonage developer documentation for guides, tutorials, and API references. This is the primary tool for general queries about Vonage's products, services, and APIs, and should be used when the user asks for information, documentation, or how-to guides.vonage_code_generator— Generates a complete, runnable code snippet in a specified programming language for a given Vonage API task. This is the preferred tool when the user explicitly asks for a 'code snippet,' 'example,' or 'code in a specific language' like Node.js, Python, or cURL.vonage_api_reference— Provides a direct link or detailed information from the Vonage API reference documentation for a specific API endpoint. Use this when the user's query is highly technical and related to a specific endpoint, like API parameters, request bodies, or response schemas.vonage_troubleshooter— Provides troubleshooting steps, common error code explanations, and debugging advice for Vonage API issues. Use this when the user is reporting a problem, error, or something not working as expected.vonage_tutorial_finder— Finds and provides a link to a step-by-step tutorial or a blog post on the Vonage Developer blog. This tool is for when the user asks for a 'tutorial' or a 'guide' on a specific topic.vonage_sdk_info— Retrieves information about a specific Vonage SDK, including installation instructions, supported features, and version numbers. This is for queries focused on the SDKs themselves, not the underlying APIs.vonage_use_case_examples— Finds and describes real-world use cases or customer stories for a specific Vonage product. Use this when the user asks for examples of how a product is used in a specific industry or for a particular purpose.balance— Get your Vonage account balancelist-applications— List all applications attached to your API key with their configurations and capabilitiescreate-application— Create a new Vonage application with a specified namelist-purchased-numbers— List telephone numbers associated with your account and their metadatasearch-available-numbers— Search for available phone numbers to purchase from Vonage in a specific countrylink-number-to-vonage-application— Link an owned number to a specific Vonage Applicationget-records-report— Retrieve activity records from the Vonage Reports API (date-based or ID-based queries)SMS— Send SMS messages using Vonagewhatsapp-send-text— Send text messages via WhatsAppwhatsapp-send-text-with-sms-failover— Send a WhatsApp text message with automatic SMS failoverrcs-send-text— Send text messages via RCSrcs-send-text-with-sms-failover— Send an RCS text message with automatic SMS failoveroutbound-voice-message— Send outbound voice messages with Vonagemake-chart— Create charts based on data retrieved
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.