Vonage AI Assist MCP Server

Created By
micahman33a year ago
Simple MCP server to assist in doing AI code generation in Claude Desktop/Claude Code that always works off of the newest Vonage SDKs and APIs
Overview

What is Vonage Assist?

Vonage Assist is a Model Context Protocol (MCP) server designed to help developers integrate Vonage API capabilities into their applications, providing AI-assisted access to Vonage documentation.

How to use Vonage Assist?

To use Vonage Assist, set up the server by installing Python 3.13+, configuring environment variables, and running the server. Once running, utilize the Vonage-Assist tool to search for documentation using specific queries.

Key features of Vonage Assist?

  • Documentation search tool for Vonage APIs
  • Integration with Google Serper API for targeted searches
  • Content extraction from official documentation
  • Compatibility with AI assistants supporting MCP protocol

Use cases of Vonage Assist?

  1. Quickly finding information about implementing two-factor authentication with Vonage APIs.
  2. Assisting developers in understanding API parameters and usage.
  3. Providing troubleshooting support for common integration issues.

FAQ from Vonage Assist?

  • What programming languages does Vonage Assist support?

Vonage Assist is designed to work with any programming language that can make HTTP requests to the Vonage APIs.

  • Is Vonage Assist free to use?

Yes! Vonage Assist is free to use for developers.

  • What are the system requirements for Vonage Assist?

You need Python 3.13+ and the necessary environment variables set up to run Vonage Assist.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
micahman33
Star
0
Language
Python
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)

2 days ago