Crixin places real phone calls. Real money is at stake. Here's what's actually in the box, what stays on your laptop, and where Twilio's bill ends and ours begins (it doesn't — we don't bill you).
An MCP server, a CLI, and a local SQLite database. The MCP server exposes make_call, send_sms, transcribe_call, get_call, list_calls, and list_recordings to any AI host (Claude Code, Cursor, Codex CLI, Claude Desktop). The CLI lets you place one-off calls, ingest your Twilio history, and run Voice Wrapped / Caller Archetype / Ducked analysis on your transcripts.
Your transcripts, your call recordings (which live in your Twilio account anyway), your phone numbers, your customer list, your Caller Archetype label, your Voice Wrapped report. Crixin has zero servers between you and Twilio. Calls hit api.twilio.com directly with your auth header.
Optional. Only used if you set DEEPGRAM_API_KEY and call transcribe_call (or run crixin voice ingest with transcription enabled). When you do, recordings are sent from your Twilio account → Deepgram for transcription, and the result is stored locally. Crixin doesn't see, store, or proxy any of it.
The open-source toolkit is MIT-licensed and free forever. You pay Twilio directly for the actual phone calls — typically ~$0.014/min for US/Canada outbound voice and ~$0.0083 per SMS. International is more (Egypt ~$0.135/min, UAE ~$0.155/min mobile). Deepgram is ~$0.0043/min on the Nova-2 tier. Crixin doesn't take a cut. Pro ($5/mo) adds hosted Wrapped and cross-machine memory sync — it's not a managed Twilio reseller. You always pay Twilio directly.
Voice MCP is a phone primitive. It doesn't tell you what to do with it. The toolkit ships a geo-gate (strict-consent jurisdictions like US/UK/EU/AU require an explicit consented: true flag) and TCPA-window helpers. The rest of compliance — DNC list checking, consent collection, opt-out flows — is on you, because Crixin doesn't know if your AI is running an inbound receptionist or outbound sales. Both are legitimate, both have different obligations.
Whatever Twilio's <Say> supports — Polly + Google neural voices, ~30 languages including Egyptian Arabic (Polly.Hala-Neural), MSA Arabic (Polly.Zeina), Spanish (Polly.Lucia-Neural), Portuguese, French, German, Mandarin, etc. For transcription via Deepgram, Nova-2 covers 30+ languages including all the above. ElevenLabs voice cloning is on the roadmap, not in v0.1.0.
STT: Deepgram (optional, only when you ask). TTS: Twilio Polly + Google neural voices (built into Twilio's <Say> verb). LLM: there's no LLM in the call path — your AI host (Claude/GPT/etc.) decides what to say, and Voice MCP just speaks it. Bring your own LLM, always.
From your local SQLite (~/.crixin/crixin.db), populated by crixin voice ingest which mirrors your Twilio Calls + Recordings into the voice_calls + voice_recordings tables. If DEEPGRAM_API_KEY is set, it also runs Deepgram on each recording and rolls the transcripts up onto the call row. The Wrapped HTML is rendered from those rows entirely client-side — no network call to generate the report.
v0.1.0 retired it. Older versions of crixin ingested Claude Code / Codex CLI / Cursor JSONL session files and ran a wrapped/archetype analysis on coding sessions. That product is no longer the focus — same engines now read call data instead. If you were on v0.0.x and want to keep the session-analyzer flow, pin to crixin@0.0.9 in your install.
Yes — that's the point of MCP. Anything that talks the Model Context Protocol (Claude Code, Cursor, Codex CLI, Claude Desktop, and a growing list of others) can use Crixin's tools. The voice MCP server is stdio-based, ships as a single npm package, and reads creds from env. No HTTPS endpoints to expose, no public webhooks to register with Twilio.
Pro ($5/mo, 3-day free trial) unlocks: hosted Wrapped share links (revocable), cross-machine memory sync (same Coder MCP history on every laptop you work from), and premium archetypes. That's the whole upsell. No enterprise tier, no sales team, no SLA. The open-source toolkit stays MIT and free for everyone.
make_call 401s. What do I do?Re-copy your token from console.twilio.com into your secrets manager + restart your AI host so it picks up the new env. Then run crixin voice doctor — it'll do a single GET against the Twilio API and tell you "active" or surface error 20003 with the exact reason. No charges, no risk. (This is the most common production failure for any Twilio-backed product. We surface it as a friendly message instead of raw JSON in case it happens mid-call.)