Telephony MCP Server

If you already use Telephony, the telephony mcp server is the piece that lets your assistant work with it directly. 📖 Blog Post: Learn more about this project in the detailed blog post: Telephony MCP Server for Agentic AI and Language Models.

What the server does

This directory contains MCP (Model Context Protocol) Server tools for telephony operations, such as making voice calls and sending SMS messages using the Vonage API. These tools are designed to be integrated with Large Language Model (LLM) applications, enabling LLMs to perform real-world actions beyond simple text generation.

• Receives and stores Vonage event callbacks
• Provides endpoints to view and manage stored events
• Runs as a separate service within the same application

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Prerequisites — The Prerequisites tool exposed by this server
• Setup — 1. Install dependencies: bash pip install -r requirements.txt Or, if using Poetry: bash poetry install
• Features — The Features tool exposed by this server
• Endpoints — The Endpoints tool exposed by this server
• Configuration — To use the callback server with Vonage Voice API, you need to set the CALLBACK_SERVER_URL environment variable to your server's public URL. This URL

Credentials and setup notes

Configuration is passed through the environment: CALLBACK_SERVER_URL, VONAGE_API_KEY, VONAGE_API_SECRET, VONAGE_APPLICATION_ID, VONAGE_PRIVATE_KEY_PATH, VONAGE_API_URL, VONAGE_SMS_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.13+ - MCP CLI (mcp[cli]), FastAPI, httpx, pyjwt, python-dotenv, uvicorn, pydantic (see pyproject.toml for details) - Vonage API credentials (API key, secret, application ID, private key) - Public URL for callback server (for production use)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Telephony's toolset — Prerequisites, Setup, Features and 2 more — is a fair guide to whether it matches your workflow. It is maintained by khan2a; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Telephony's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.