Run Vomyra from Perplexity
Perplexity supports custom remote MCP connectors, and Vomyra's server matches what it expects: an HTTPS endpoint, Streamable HTTP transport and OAuth. That's all it needs to reach your assistants, calls and transcripts.
Endpoint https://console.vomyra.com/mcp · Streamable HTTP · OAuth
The short version
About 4 steps. The full guide has the screenshots and the edge cases.
- 1
Open custom connectors
In Perplexity, add a custom connector and pick “Remote” in the dialog.
- 2
Point it at Vomyra
Enter https://console.vomyra.com/mcp as the remote MCP server URL, with a short description of what it does.
- 3
Choose OAuth and Streamable HTTP
Select OAuth for authentication and Streamable HTTP as the transport — both are what Vomyra's server speaks.
- 4
Check it worked
Ask Perplexity to list your Vomyra assistants.
Try saying
Once Perplexity is connected, these prove it's working.
- “List my Vomyra assistants”
- “Summarise my most recent Vomyra call”
- “What phone numbers are routed to my support assistant?”
Worth knowing
- We don't publish a Vomyra-specific Perplexity walkthrough yet, so the guide link goes to Perplexity's own documentation. The connection details above are all Vomyra's side needs.
- Perplexity requires HTTPS for remote connectors — Vomyra's endpoint already is.
What Perplexity can reach
24 actions in total, across four areas of your Vomyra account.
Assistants10
Create, configure and manage voice assistants and their settings.
Tools6
Build and control the actions your assistants can perform on a call.
Calls5
Place outbound calls and pull conversation transcripts.
Numbers3
Inspect phone numbers and how calls route to your assistants.
