Skip to main content
Glama

voygr-mcp

MCP server for VOYGR place verification and outbound venue calls. Proper stdio MCP: tools, resources, prompts, progress notifications, and elicitation.

Demo Video

Install

cd voygr-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"

Requires a VOYGR API key at process start:

export VOYGR_API_KEY=your_key
# or: voygr login your_key

Related MCP server: vonage-mcp-server-api-bindings

Dry-run (default)

VOYGR_DRY_RUN defaults to 1. Calls only are mocked (magic numbers, scripted events, canned transcripts). verify_place / verify_places / check_credits always hit the live VOYGR API via the official voygr Python client.

Magic number

Outcome

+1-555-0100

success_booked

+1-555-0101

failed_voicemail

+1-555-0102

mid-call ask_user then success_booked

+1-555-0103

failed_short_hangup

+1-555-0104

409 concurrency cap

+1-555-0105

402 insufficient credits

Live dialing:

export VOYGR_DRY_RUN=0
docker compose up -d redis   # call state / event cursors
export VOYGR_REDIS_URL=redis://localhost:6379/0
voygr-mcp

Claude Desktop (stdio)

  1. Put VOYGR_API_KEY=... in the project .env (loaded automatically; Claude’s cwd does not matter).

  2. Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) and merge:

{
  "mcpServers": {
    "voygr": {
      "command": "/Users/vaarunsinha/voygr-mcp/scripts/claude-desktop-mcp.sh",
      "env": {
        "VOYGR_DRY_RUN": "1"
      }
    }
  }
}
  1. Fully quit and reopen Claude Desktop. Confirm under + → Connectors (or Developer settings) that voygr is connected and tools like verify_place appear.

Or point command at .venv/bin/voygr-mcp directly — the server also loads the package-root .env on start.

Tools

Tool

Role

verify_place

Single POI → agent-safe verdict (not raw open/closed)

verify_places

Batch + normalized cache

call_place

Structured call (inquiry / info_gathering); consent + slots elicited

get_call

Resume by call handle

check_credits

Usage / credits

Consent is never a tool parameter — it is always an elicitation to the human.

Resources / prompt

  • voygr://call/{id}/transcript — 7-day retention noted in metadata

  • voygr://call/{id}/events

  • Prompt: verify_before_recommending

Honesty (demo / video)

When recording the 60s demo:

  • Refusal arm (verify_places dropping closed/not_found) should be live API.

  • Mid-call handoff segment should be dry-run (+1-555-0102) and labeled on screen.

  • List which segments used dry-run in any public write-up.

Tests

pytest

Tests use ScriptedElicitationProvider (no human). No skip-consent env var ships in the server.

Stack

Python, official mcp SDK (stdio), voygr PyPI client, httpx (calls API), Redis (live call state), Docker Compose, pytest. No FastAPI in v1.

Reference checkout of upstream CLI (not vendored): ../voygr-dev-tools.

Install Server
A
license - permissive license
A
quality
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • Official MCP server for OmniDimension. Drive voice agents, dispatch calls, and run bulk campaigns.

  • MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting.

  • MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VaarunSinha/voygr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server