Voyp

Provides two-way MCP access to Voyp call capabilities for initiating, monitoring, and terminating calls with business data lookups
  • javascript

9

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

The Voyp Model Context Protocol (MCP) server lets your AI assistant interact with Voyp’s calling capabilities by establishing secure, two-way connections to data sources and tools. With MCP you can construct call contexts, search for business information, place calls, manage call progress, and end calls from your AI workflows.

How to use

You connect an MCP client to the Voyp MCP server to enable phone-based interactions from your AI assistant. Use the HTTP stream endpoint for remote access and a local stdio setup to run the server inside your client workflow. Once connected, you gain access to tools that let you start calls, monitor status, perform lookups, and hang up when finished.

Typical usage patterns include configuring a client to the HTTP stream for live calls or starting a local stdio server during development. In your MCP client, initiate a call with start_call, monitor its progress with status or related tools, and close the session with hangup_call when you’re done.

How to install

Prerequisites: You need a Voyp API key, sufficient call credits, a compatible MCP client (Claude Desktop, Goose, or other MCP-enabled client), and Node.js version 20 or higher. Verify your Node.js installation with node --version.

Install options fall into two tracks: connect via remote HTTP stream or run a local stdio server. The HTTP stream is hosted remotely and accessed with an MCP URL. The local stdio server runs inside your environment using a command that starts the Voyp MCP process.

If you will use the Claude Desktop app with Voyp MCP, you can install or run the server via NPX or clone and build it locally as needed. The NPX approach lets you start the server quickly without a local build.

Additional sections

MDP/endpoint configuration and security: You must provide your Voyp API key via environment variables in your MCP client configuration. Use the Authorization header for the HTTP stream endpoint when connecting directly to Voyp.

Example environment variable for the stdio setup: VOYP_API_KEY=YOUR_API_KEY.

Troubleshooting tips cover common issues like server not found, npx-related errors, and API key validation. Ensure your Node.js and npm/npx are properly installed and that your configuration JSON is correctly formatted.

Tools and capabilities

You gain access to a set of tools for managing calls, including starting a call, checking status, and hanging up the call. These tools enable you to construct call contexts, search for business information, and manage appointment-related interactions.

Available tools

start_call

Initiates a new phone call using Voyp MCP, creating a call context and returning identifiers for monitoring.

status_call

Reports on the current status of an ongoing call, including progress and any updates from Voyp.

hangup_call

Terminates an active call and releases resources associated with the call context.

construct_context

Builds a call context with relevant details (destination, purpose, scheduling) to use when initiating a call.

search_info

Performs business lookups (e.g., restaurants, doctors) to inform call outcomes and scheduling.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational