Skip to main content
Glama
Voyp MCP Server

Voyp MCP Server

by paulotaylor

Voyp Model Context Protocol server

The Model Context Protocol (MCP) is an open standard that enables AI systems to interact seamlessly with various data sources and tools, facilitating secure, two-way connections.

Developed by Anthropic, the Model Context Protocol (MCP) enables AI assistants like Claude to seamlessly integrate with VOYP's calling capabilities. This integration provides AI models with possibility of making phone calls and monitor their progress.

The Voyp MCP server allows you to:

  • Construct robust call contexts to use when making calls

  • Search for business information when calling restaurants, dentists, etc...

  • Call and make appointments, reservations, consultations, inquiries, etc...

  • Provide status of the call

  • Hangup call

Voyp skill for AI agents 🧠

This repository includes a Voyp skill (skills/voyp) in the Agent Skills format. The MCP server gives an agent the tools to make calls. The skill teaches it how to use them well: find and check the number, write a full call briefing, ask the user before every call, follow the call live, and report the result. It works in Claude Code, the Claude apps, the Claude API, and other agents that support skills.

Quick install for Claude Code (installs the skill and the hosted Voyp MCP server):

/plugin install voyp --marketplace paulotaylor/voyp-mcp

On older Claude Code versions, run /plugin marketplace add paulotaylor/voyp-mcp, then /plugin install voyp@voyp. Afterwards run /mcp and sign in to Voyp.

For other agents:

npx skills add paulotaylor/voyp-mcp

See docs/SKILL.md for every install method (Claude Code, claude.ai and Claude Desktop, Claude API, Codex, Cursor and other agents), usage, and troubleshooting.

Related MCP server: bubblyphone-agents

Prerequisites 🔧

Before you use Voyp, you need:

  • Voyp API key

    • You will also need to buy credits to spend while making calls. You can also buy credits here

  • Claude Desktop, Goose or other compatible clients

  • Node.js (v20 or higher)

    • You can verify your Node.js installation by running:

      • node --version

  • Git installed (only needed if using Git installation method)

    • On macOS: brew install git

    • On Linux:

      • Debian/Ubuntu: sudo apt install git

      • RedHat/CentOS: sudo yum install git

    • On Windows: Download Git for Windows

Remote Voyp MCP server (Http Streamable)

You can connect directly to the stream-enabled endpoint here:

https://api.voyp.app/mcp/stream

It accepts two kinds of credentials in the Authorization header:

  • OAuth 2.1 (recommended for apps such as Claude, ChatGPT or Claude Code): connect without a token and the client signs you in to Voyp in the browser. The server publishes its OAuth metadata at https://api.voyp.app/.well-known/oauth-protected-resource.

  • Voyp API key: for clients that let you set headers (Goose, Cursor, scripts, agent SDKs). Get your key at voyp.app:

Authorization: Bearer sk_xyz

An API key gives full access to your Voyp account, so keep it secret.

Example client config with an API key:

{
  "mcpServers": {
    "voyp": {
      "type": "http",
      "url": "https://api.voyp.app/mcp/stream",
      "headers": { "Authorization": "Bearer sk_xyz" }
    }
  }
}

Voyp MCP server installation for Goose ⚡ (Stdio)

To install the voyp-mcp server you will need to add the extension manually.

Adding VOYP MCP server to Goose

Voyp + Goose Demo:

Voyp + Goose Demo

Voyp MCP server installation for Claude Desktop ⚡ (Stdio)

To install the voyp-mcp server, you can use the following methods:

  1. Installing via Smithery

  2. Running with NPX

  3. Git installation

1. Installing via Smithery

To install Voyp Model Context Protocol server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @paulotaylor/voyp-mcp --client claude

2. Running with NPX

npx -y voyp-mcp@0.1.0   

Although you can launch a server on its own, it's not particularly helpful in isolation. Instead, you should integrate it into an MCP client. Below is an example of how to configure the Claude Desktop app to work with the voyp-mcp server.

Configuring the Claude Desktop app ⚙️

For macOS:

# Create the config file if it doesn't exist
touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

# Opens the config file in TextEdit 
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

# Alternative method using Visual Studio Code (requires VS Code to be installed)
code "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

For Windows:

code %APPDATA%\Claude\claude_desktop_config.json

Add the Voyp server configuration:

Replace your-VOYP-api-key with your actual VOYP API key.

{
  "mcpServers": {
    "voyp-mcp": {
      "command": "npx",
      "args": ["-y", "voyp-mcp"],
      "env": {
        "VOYP_API_KEY": "your-VOYP-api-key"
      }
    }
  }
}

3. Git Installation

  1. Clone the repository:

git clone https://github.com/paulotaylor/voyp-mcp.git
cd voyp-mcp
  1. Install dependencies:

npm install
  1. Build the project:

npm run build

Configuring the Claude Desktop app ⚙️

Follow the configuration steps outlined in the Configuring the Claude Desktop app section above, using the below JSON configuration.

Replace your-VOYP-api-key-here with your actual VOYP API key and /path/to/voyp-mcp with the actual path where you cloned the repository on your system.

{
  "mcpServers": {
    "voyp": {
      "command": "npx",
      "args": ["/path/to/voyp-mcp/build/index.js"],
      "env": {
        "VOYP_API_KEY": "your-VOYP-api-key"
      }
    }
  }
}

Usage in Claude Desktop App 🎯

Once the installation is complete, and the Claude desktop app is configured, you must completely close and re-open the Claude desktop app to see the voyp-mcp server. You should see a hammer icon in the bottom left of the app, indicating available MCP tools, you can click on the hammer icon to see more details on the start_call and hangup_call tools.

Now claude will have complete access to the voyp-mcp server, including the start_call and hangup_call tools.

Voyp + Claude Desktop Demo:

Voyp + Claude Desktop Demo

Troubleshooting 🛠️

Common Issues

  1. Server Not Found

    • Verify the npm installation by running npm --verison

    • Check Claude Desktop configuration syntax by running code ~/Library/Application\ Support/Claude/claude_desktop_config.json

    • Ensure Node.js is properly installed by running node --version

  2. NPX related issues

  • If you encounter errors related to npx, you may need to use the full path to the npx executable instead.

  • You can find this path by running which npx in your terminal, then replace the "command": "npx" line with "command": "/full/path/to/npx" in your configuration.

  1. API Key Issues

    • Confirm your VOYP API key is valid

    • Check the API key is correctly set in the config

    • Verify no spaces or quotes around the API key

Acknowledgments ✨

Available Tools

7 tools
get_callC

Retrieve call details

Inputs: id (required).

get_userB

Retrieve user profile

Inputs: no named parameters.

hangup_callC

Hangup an existing call

Inputs: id (required).

search_placeC

Search place details in a given location

Inputs: place (required), location (required).

search_place_by_numberB

Find place name and address by phone number

Inputs: number (required).

search_placesC

Search places in a given location

Inputs: search (required).

start_callC

Start a new phone call via Voyp API. The API returns the call id and a URL where users can track the progress of the call

Inputs: number (required), context (required), language.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation3/5

    The tools have some clear distinctions, such as get_call vs. hangup_call vs. start_call for call operations, but there is significant overlap between search_place, search_places, and search_place_by_number, which could cause confusion about which to use for location-based searches. The descriptions help clarify, but the boundaries are not perfectly distinct.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., get_call, get_user, hangup_call, start_call), with clear and readable naming. However, the search tools have minor deviations (search_place, search_places, search_place_by_number), which slightly disrupts the pattern but remains mostly consistent.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a server focused on phone calls and place searches. Each tool appears to serve a specific purpose without unnecessary duplication, fitting within the typical 3-15 range for a coherent toolset.

    Completeness3/5

    For call operations, there is good coverage with get, start, and hangup, but missing update or list operations for calls or users could be a gap. For place searches, the tools cover various search methods, but without create or delete operations, the surface feels incomplete for a full lifecycle in the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers