Voice Assistant MCP Server

Created By
prakharbhardwaja year ago
A Model Context Protocol (MCP) server that integrates Twilio Voice, Deepgram AI, and OpenAI to create intelligent voice-based HR automation tools.
Overview

what is Voice Assistant MCP Server?

Voice Assistant MCP Server is a powerful Model Context Protocol (MCP) server that integrates Twilio Voice, Deepgram AI, and OpenAI to create intelligent voice-based HR automation tools. It enables AI assistants to conduct phone interviews, deliver notifications, and manage HR communications through natural voice conversations.

how to use Voice Assistant MCP Server?

To use the Voice Assistant MCP Server, clone the repository, install dependencies, configure environment variables, and start the web server. You can then integrate it with Claude Desktop for voice interactions.

key features of Voice Assistant MCP Server?

  • AI-Powered Voice Interviews: Conduct professional phone interviews with candidates using AI.
  • Interview Result Notifications: Automatically call candidates with interview results and feedback.
  • Job Opportunity Outreach: Reach out to potential candidates about new positions.
  • Real-time Voice Processing: Powered by Deepgram’s Voice Agent API.
  • Comprehensive Logging: Detailed logging for debugging and monitoring.

use cases of Voice Assistant MCP Server?

  1. Conducting voice interviews with job candidates.
  2. Notifying candidates about their interview results.
  3. Reaching out to potential candidates for job openings.
  4. Managing HR communications through voice interactions.

FAQ from Voice Assistant MCP Server?

  • What are the prerequisites for setting up the server?

You need Node.js, a Twilio account, a Deepgram account, and a public URL for webhooks.

  • Is there a way to debug issues?

Yes! You can enable detailed logging and check the console output for troubleshooting.

  • Can I add new tools to the MCP server?

Yes! You can define new tools in the tools.js file and implement their logic accordingly.

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

a day ago