io. github. Vonage/ vonage-documentation-mcp
by Vonage · remote · no sign-in to list tools · v1.0.0 · published by GitHub user Vonage
MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting.
7 tools: 3 change things and 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things3Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http vonage-documentation https://documentation-mcp.vonage.dev/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
7 tools
Changes things 3Claude Code: ask
vonage_api_referenceProvides a direct link or detailed information from the Vonage API reference documentation for a specific API endpoint.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_code_generatorGenerates a complete, runnable code snippet in a specified programming language for a given Vonage API task.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it 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_troubleshooterProvides troubleshooting steps, common error code explanations, and debugging advice for Vonage API issues.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 4Claude Code: allow
vonage_docs_searchSearches the official Vonage developer documentation for guides, tutorials, and API references.No findings
Why it is in this group
- The name "vonage_docs_search" says "search": a word for reading.
Description, as the server wrote it 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_sdk_infoRetrieves information about a specific Vonage SDK, including installation instructions, supported features, and version numbers.No findings
Why it is in this group
- The description's first verb is "retrieve": a word for reading.
Description, as the server wrote it 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_tutorial_finderFinds and provides a link to a step-by-step tutorial or a blog post on the Vonage Developer blog.No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it 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_use_case_examplesFinds and describes real-world use cases or customer stories for a specific Vonage product.No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vonage-documentation https://documentation-mcp.vonage.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vonage-documentation__vonage_docs_search",
"mcp__vonage-documentation__vonage_tutorial_finder",
"mcp__vonage-documentation__vonage_sdk_info",
"mcp__vonage-documentation__vonage_use_case_examples"
],
"ask": [
"mcp__vonage-documentation__vonage_code_generator",
"mcp__vonage-documentation__vonage_api_reference",
"mcp__vonage-documentation__vonage_troubleshooter"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as vonage-documentation. Review it before you use it.
