MCP Integration
Connect Myra to the tools you already use � and let AI tools like Claude manage Vomyra � all through a shared open standard.
What is MCP?
MCP stands for Model Context Protocol. It is an open standard that lets AI apps and tools talk to each other in a common language. In Vomyra, MCP works two ways: it lets your voice assistants use tools from other services, and it lets AI tools like Claude manage Vomyra on your behalf.
Think of MCP like a universal adapter. Instead of building a custom connection for every AI app or service you want to connect, MCP gives both sides a shared format � so anything that supports MCP just works together.
Vomyra as an MCP client
Myra needs real information mid-call � like checking a customer's order or creating a support ticket. MCP Client lets her reach out to tools like Linear, Notion, GitHub, or your own systems.
Vomyra as an MCP server
You want to manage your Vomyra setup using an AI tool like Claude or Cursor � creating assistants, starting calls, reviewing transcripts � all through conversation instead of clicking through a dashboard.
Why use MCP?
Use MCP whenever Myra needs to go beyond conversation � looking things up, taking actions, or letting AI tools manage your setup. It keeps everything structured, secure, and easy to maintain.
Myra can actually do things
Instead of just talking, Myra can look up a real order, book an appointment, file a ticket, or trigger a workflow � all during a live conversation.
Manage Vomyra by just asking
Connect Claude or Cursor to Vomyra and tell it what you want in plain English � 'list my assistants', 'change the voice to Hindi', 'start a call'. No dashboard clicking required.
You stay in control
Each connection is tied to your account only. Whatever AI tool connects through MCP can only see and change your data � nothing else.
One standard, everything works
Because MCP is an open standard, any tool that supports it connects to Vomyra without extra coding � no building a separate integration for each new app.
How it works
Whether you're connecting tools to an assistant or connecting Claude to Vomyra, the setup follows the same four steps.
Figure out what you need
Does your voice assistant need to look things up mid-call? Use MCP Client. Do you want to manage Vomyra from Claude or your own code? Use MCP Server.
Connect and sign in
Use OAuth (the familiar 'sign in' button) for tools like Claude, or paste in an API key for backend automation. Either way, it takes under a minute.
Choose what it can do
Decide which actions Myra or the client is allowed to take � like checking calendars or creating tickets � so nothing happens outside that approved list.
Try it before going live
Send a test request, check the responses, and make sure everything works as expected before your real users start calling.
OAuth 2.1 (Sign in with Vomyra)
Best for connecting AI toolsThe familiar 'sign in' flow � click to authorize, and the AI client gets access automatically. No passwords shared, tokens refresh silently.
API Key
Best for code and automationGenerate a key from your dashboard and include it in requests. Great for scripts, backend apps, or developer tools like Cursor.
What Vomyra MCP can control
Vomyra's MCP server gives AI tools access to 24 actions and 3 read-only data views � all scoped to your account.
Assistants
10 toolsCreate, update, list, and delete your voice assistants � including voice, language, and AI model settings.
Tools
6 toolsBuild and manage the actions your assistants can take, like API lookups or form submissions.
Calls
5 toolsKick off outbound calls, review call history, and read full conversation transcripts.
Numbers
3 toolsSee your phone numbers and connect them to the right assistant.
When to use each MCP option
Start with the outcome you want. Not sure which to pick? Think of it this way: MCP Client is for Myra to use tools, MCP Server is for AI tools to manage Vomyra.
When Myra needs external tools
Myra is live on a call and needs to look something up or take action in another system � like checking a CRM record or filing a support ticket.
- Check a customer record in your CRM
- Create or update a support ticket
- Read a calendar or project management task
- Call a custom internal API through your MCP server
When another AI client needs to manage Vomyra
You want to manage your Vomyra setup from an AI tool like Claude or Cursor � or build automation that controls Vomyra programmatically.
- List and update Vomyra assistants
- Create or attach assistant tools
- Start outbound calls
- Review call transcripts and call details
Safety and access
Whatever AI tool connects through MCP can only see and manage your own Vomyra data � your assistants, tools, calls, and numbers. It cannot touch another user's account, your billing details, subscription settings, or any account-wide admin controls.
- Endpoint
- https://vomyra.com/mcp
- Transport
- Streamable HTTP (POST JSON-RPC 2.0)
- Server name
- vomyra
- Version
- 1.0.0
Quick reference
Endpoint: POST https://vomyra.com/mcp
Transport: Streamable HTTP (JSON-RPC 2.0)
Auth: OAuth 2.1 (mcp:tools) | x-api-key
Limits: 30 req/min unauth | 600 req/min auth | 256 KB body
OAuth discovery:
GET /.well-known/oauth-authorization-server
GET /.well-known/oauth-protected-resource/mcp
Token TTL: access 1 h | refresh 30 d