Manage your voice agents from Claude with the Vaakyo MCP server
Connect Claude, Cursor or another MCP client to Vaakyo and manage agents, calls and campaigns in plain language, with scoped OAuth access.
The Vaakyo team2 min read
- MCP
- Developers
The Model Context Protocol (MCP) lets AI apps use other products as tools. Vaakyo runs an MCP server, so an assistant like Claude can list your agents, read calls and transcripts, edit an agent or start a test call when you ask it to.
Connect
Add Vaakyo as a custom connector (or MCP server) in your client with this URL:
https://console.vaakyo.com/mcp
It uses the Streamable HTTP transport. The first time, your client opens a Vaakyo page where you sign in, choose the workspace and allow the connection. There are no API keys to copy.
Grant only what's needed
Connections use OAuth scopes. An app can ask for exactly what it needs, for example agents.view calls.view for a read-only assistant that answers questions about your calls, or mcp for everything an API key may do. A connection can never do more than your own role allows, and you can disconnect it any time from Settings in the console.
Things to ask
- "Summarise yesterday's failed calls for the COD agent and tell me what went wrong."
- "Which calls this week ended in a transfer, and why?"
- "Add a question about delivery time to the feedback agent's prompt."
- "Show the extracted fields for the last ten calls as a table."
Actions that cost money or reach the outside world, such as placing calls, still need your confirmation in the client.
For developers
Everything the MCP server does goes through the same public API as your integrations, with the same permissions, limits and audit log. If you're building your own agent rather than using a client, the API reference and the MCP quickstart cover the details, including the OAuth endpoints and scopes.
