Set webhook URL to your tunnel URL + /webhook/twilio/whatsapp
Get your Account SID and Auth Token
Baileys connects directly to WhatsApp's Web protocol via WebSocket. It uses your personal WhatsApp account — no business verification, no API costs, no Twilio/Telnyx required.
How it works: Same as WhatsApp Web — you link a device by scanning a QR code.
Step 1: Clone and install
git clone https://github.com/sns45/better-call-claude
cd better-call-claude
bun install
Step 2: Pair your WhatsApp
bun run baileys:pair
A QR code will appear in your terminal
Open WhatsApp on your phone > Settings > Linked Devices > Link a Device
Scan the QR code
Wait for "Paired successfully!" message
Your session is saved in data/baileys-auth/ — you won't need to scan again.
Step 3: Add to Claude Code (~/.claude.json or ~/.claude/settings.json):
That's it! No Tailscale, no Twilio, no OpenAI keys needed.
Step 4: Restart Claude Code and test
Send a WhatsApp message to yourself (or have someone message you) — Baileys receives it and spawns a Claude task. Or ask Claude to send you a WhatsApp:
"Send me a WhatsApp saying hello"
Get the best of both worlds: Twilio/Telnyx handles voice calls and SMS, Baileys handles WhatsApp for free.
Note: Tailscale setup is automatic on first run. The server will guide you through installation and authentication if needed.
Restart Claude Code. Done!
Environment Variables
Required Variables
Variable
Description
BETTERCALLCLAUDE_PHONE_PROVIDER
telnyx or twilio
BETTERCALLCLAUDE_PHONE_ACCOUNT_SID
Provider account/connection ID
BETTERCALLCLAUDE_PHONE_AUTH_TOKEN
Provider API key/auth token
BETTERCALLCLAUDE_PHONE_NUMBER
Your Telnyx/Twilio phone number (E.164)
BETTERCALLCLAUDE_WHATSAPP_NUMBER
WhatsApp number if different (e.g., Twilio Sandbox)
BETTERCALLCLAUDE_USER_PHONE_NUMBER
Your personal phone number
BETTERCALLCLAUDE_OPENAI_API_KEY
OpenAI API key for TTS/STT
Baileys (Free WhatsApp)
Variable
Default
Description
BETTERCALLCLAUDE_WHATSAPP_PROVIDER
(unset)
Set to baileys to enable free WhatsApp
BETTERCALLCLAUDE_BAILEYS_AUTH_DIR
data/baileys-auth
Session credential directory
Baileys-only mode: When WHATSAPP_PROVIDER=baileys and no Twilio/Telnyx credentials are set, only USER_PHONE_NUMBER is required. No Tailscale, no OpenAI key needed.
🤖 "Build failed on line 42 of auth.ts. Reply with 'fix' to auto-fix or 'skip' to continue."
WhatsApp
You → Claude (Inbound WhatsApp)
Send a WhatsApp message to your business number:
💬 "Show me the error logs from the last hour"
Claude responds in WhatsApp:
🤖 "Found 3 errors:\n1. Connection timeout at 14:32\n2. Auth failure at 14:45\n3. Rate limit at 15:01\n\nWant me to investigate any of these?"
Claude → You (Outbound WhatsApp)
Claude can send rich WhatsApp messages:
🤖 "Code review complete! Found 2 issues:\n• Line 23: Unused variable\n• Line 67: Missing error handling\n\nReply 'fix' to auto-fix or 'details' for more info."
Cross-Channel Context
Start a task on voice and seamlessly continue on WhatsApp - Claude remembers everything.
Example Flow
Call Claude:
📞 "Hey Claude, run the todo app in dev mode and let's continue on WhatsApp"
Claude starts the app and enters WhatsApp listening mode:
🤖 "Todo app running on port 5173. Send me WhatsApp messages for more instructions."
Send WhatsApp message:
💬 "Expose it via localtunnel and add the URL to allowed hosts"
Claude responds via WhatsApp:
🤖 "Done! Localtunnel URL: https://xyz.loca.lt - I've added it to vite.config.ts allowedHosts"
Continue the conversation:
💬 "What's the public IP so I can access it remotely?"
Typical WhatsApp exchange: Free (Baileys) or ~$0.01-0.02 (Twilio/Telnyx)
Infrastructure
Service
Cost
Phone number
~$1/month
Tailscale Funnel
Free
Security Considerations
Tailscale Funnel Security
Funnel creates a public endpoint but traffic routes through Tailscale's secure network
Integrates with SSO/SCIM for enterprise use
Audit logs available in Tailscale admin console
Webhook signatures verified by default
General
Phone numbers are never logged
Call transcripts are ephemeral (cleared on restart)
Use environment variables, never hardcode credentials
Capability attestation
This repo ships a smithmark capability manifest, smithmark.yaml, at the repo root. It is a "trust as code" declaration of everything this server touches outside its own process: the network hosts it egresses to (Twilio, Telnyx, OpenAI, WhatsApp/Baileys infrastructure, and, transitively, api.anthropic.com via the spawned claude subprocess), the filesystem paths it reads/writes (Baileys auth state, spawn debug logs), the binaries it executes (claude, tailscale, which, open, sudo), the environment variables it reads, and the secret types it handles (Twilio, Telnyx, and OpenAI API keys).
On every GitHub release, .github/workflows/smithmark-attest.yml produces a keyless Sigstore attestation over the published npm tarball: GitHub's OIDC token is exchanged for a short-lived Fulcio signing certificate, the attestation is signed with it, and the signature is recorded in the public Rekor transparency log. There are no signing keys and no secrets involved. The resulting smithmark-attestation.sigstore.json is attached to the GitHub release.
smithmark.yaml is the authoritative declaration of this server's capability surface. smithmark lint (and verify in strict mode) is deliberately host-unaware: it flags every network/exec/filesystem call site as a generic "undeclared" finding regardless of what the manifest declares at the host level, so it will report advisory findings against any real MCP server that talks to the network. Those findings are expected noise, not a sign the manifest is out of date; the manifest above is the record to trust.
Troubleshooting
Voice Issues
Claude doesn't answer calls
Check the MCP server is running: claude --debug
Verify webhook URL is configured in provider dashboard
Ensure Tailscale Funnel is active
Can't make outbound calls
Verify BETTERCALLCLAUDE_USER_PHONE_NUMBER is correct
Check phone number is verified with provider
Ensure sufficient balance in provider account
Audio quality issues
Check network connectivity
Try different TTS voice: BETTERCALLCLAUDE_TTS_VOICE=nova
Check tailscale funnel status shows /bcc pointing to your port
Verify your phone provider webhook URL matches the Tailscale URL (with /bcc path)
Test with curl https://your-hostname.ts.net/bcc/health
Development
# Clone the repo
git clone https://github.com/sns45/better-call-claude
cd better-call-claude
# Install dependencies
bun install
# Run in development mode
bun run dev
Testing locally
# Start the MCP server
bun run dev
# In another terminal, test with MCP inspector
npx @anthropics/mcp-inspector