voygr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VOYGR_API_KEY | Yes | VOYGR API key required at process start. | |
| VOYGR_DRY_RUN | No | Dry-run mode. Defaults to 1. Set to 0 for live dialing. | 1 |
| VOYGR_REDIS_URL | No | Redis URL for live call state/event cursors. Needed when VOYGR_DRY_RUN=0. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_placeA | Verify whether a named place at an address exists and is operating. Returns verdict/recommend — never trust raw open_closed alone. Costs 1 credit. |
| verify_placesA | Verify multiple places. Input a list of {name, address}. Deduped/cached on normalized name+address. Use before recommending options. |
| call_placeA | Place a structured outbound VOYGR call to a venue phone. Intents: inquiry | info_gathering. Language: en only. For inquiry, slots MUST include question (a free-text ask for the venue). party_size/date/time alone are not enough. Consent is elicited when the client supports it; otherwise the tool returns consent_required + consent_token — ask the human in chat, then call approve_call. If the venue asks something mid-call, the tool may return awaiting_mid_call_answer — ask the human that question in chat, then answer_mid_call. No confirm boolean. In dry-run, inquiry calls simulate a live venue including mid-call questions. |
| approve_callA | Approve a pending call after the human said yes in chat. Pass the consent_token returned by call_place when error=consent_required. Only works with a server-issued token — do not invent one. |
| answer_mid_callA | Relay the human's answer to a mid-call venue question. When call_place/approve_call returns status=awaiting_mid_call_answer, show question to the human in chat, then call this with answer_token + their answer. This is the mid-call handoff — do not invent the answer or the token. |
| get_callA | Get status/outcome for a call handle returned by call_place (async recovery path). |
| check_creditsA | Report VOYGR usage/credits so the agent can explain spend and holds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| verify_before_recommending | Instructions to verify places before recommending or booking. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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