Voice Call MCP Server

Created By
lukaskaia year ago
Overview

what is Voice Call MCP Server?

Voice Call MCP Server is a Model Context Protocol (MCP) server that enables AI assistants like Claude to initiate and manage voice calls using Twilio and OpenAI.

how to use Voice Call MCP Server?

To use the Voice Call MCP Server, clone the repository, install the necessary dependencies, configure your environment variables, and run the server. You can then interact with the server through AI assistants to make voice calls.

key features of Voice Call MCP Server?

  • Make outbound phone calls via Twilio 📞
  • Process call audio in real-time with OpenAI 🎙️
  • Pre-built prompts for common calling scenarios (like restaurant reservations) 🍽️
  • Automatic public URL tunneling with ngrok 🔄
  • Secure handling of credentials 🔒

use cases of Voice Call MCP Server?

  1. Initiating phone calls for scheduling appointments.
  2. Making restaurant reservations through voice commands.
  3. Conducting real-time conversations using AI assistants.

FAQ from Voice Call MCP Server?

  • What is the required phone number format?

All phone numbers must be in E.164 format (e.g., +11234567890).

  • Do I need a Twilio account?

Yes, a Twilio account with API credentials is required to make calls.

  • Is the server open-source?

Yes, the Voice Call MCP Server is open-source and available on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lukaskai
Star
5
Language
TypeScript
License
MIT license
Tags

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)

a day ago