Krystal Voice Caller
Operate Krystal Voice Caller campaigns—calls, tenants, and API actions—from Claude or Cursor without building a custom admin UI first.
Overview
io.github.KrystalUnity/kvc-mcp is an MCP server for the Build phase that lets agents drive a Krystal Voice Caller tenant via authenticated admin API tools.
What is this MCP server?
- Drives a Krystal Voice Caller tenant from MCP-aware agents
- PyPI package kvc-mcp 0.1.1 with stdio transport
- Requires secret KVC_API_TOKEN (kvc_token_ prefix) from the Krystal Unity dashboard
- Optional KVC_BASE_URL override defaulting to https://krystalunity.com/api/admin/kvc
- Official site: krystalunity.com/voice/krystal-caller
- PyPI package: kvc-mcp version 0.1.1
- Required env: KVC_API_TOKEN; optional KVC_BASE_URL default https://krystalunity.com/api/admin/kvc
- Repository: github.com/KrystalUnity/kvc-mcp
What problem does it solve?
You want voice outbound in your agent workflow but do not want to hand-code every KVC admin API call.
Who is it for?
Solo builders already on Krystal Voice Caller who live in Claude Code or Cursor for ops automation.
Skip if: Teams without a KVC account, or projects that need generic Twilio-style low-level telephony only.
What do I get? / Deliverables
Your agent can manage Krystal Voice Caller tenant actions through stdio MCP after you add a dashboard API token.
- Agent-callable tools against your KVC tenant admin API
- Voice workflow automation without a custom internal admin panel
Recommended MCP Servers
Journey fit
Voice outbound integrations are built when you wire product workflows to a telephony provider, then reused in growth and ops. Integrations subphase is where third-party SaaS APIs (here KVC) get MCP wrappers for agent-driven automation.
How it compares
Vendor-specific voice-campaign MCP bridge—not a multi-carrier CPaaS abstraction.
Common Questions / FAQ
Who is kvc-mcp for?
Indie builders using Krystal Voice Caller who want MCP tools to run tenant and call workflows from their coding agent.
When should I use kvc-mcp?
When integrating voice outreach into build, launch, or support automations and you already have KVC API access.
How do I add kvc-mcp to my agent?
pip install kvc-mcp, set required env KVC_API_TOKEN from https://krystalunity.com/voice/krystal-caller/dashboard/api-tokens, add the stdio server to your MCP config, and optionally set KVC_BASE_URL.