V

vonage.com

8 integrations · MCP · REST · CLI

Vonage exposes five documented Vonage Business Cloud HTTP APIs (Account, Extension, Reports, User, and Integration Suite) authenticated with a required bearer token tied to subscribed API suites, plus a public documentation MCP server, a credentialed Server API Bindings MCP server, and the Vonage CLI, both configured with your Vonage API key/secret together with an application ID/private key.

discovered 1d ago
MCP servers2
REST · OpenAPI5
CLI1
Credentials
Vonage Business Cloud bearer access tokenbearerGet token ↗

For Vonage Business Cloud APIs, your application must be subscribed to the relevant API suite (for example Provisioning, Reports, or Vonage Integration Suite) before use. The published OpenAPI specs require bearerAuth, but the public docs scraped here do not show a self-service token mint page. Start from Vonage Business Cloud Support to request access and token issuance details for your tenant/application.

Vonage API key and API secretbasicGet credentials ↗

Sign up for a Vonage account, then open Account Settings in the dashboard. Vonage creates an API key and API secret for your account automatically. Use them directly where a product accepts basic auth, or pass them to tools that need API_KEY/API_SECRET. Keep the secret private.

Vonage application ID and private keycompoundGet key ↗

Open Vonage Dashboard Applications and create or select an application. Copy the application ID and download or regenerate the private key when available. These are used together by the CLI and tooling MCP server, and can also be used to mint Vonage JWTs.

conventions · 0/8 published

Publish these signals → /publishing