Most messaging servers stop at send a message. This one carries the operational half as well — buying and routing numbers, registering 10DLC brands and campaigns, reading CDRs and call transcripts — which is where the working day actually goes. Wavix suggests a key scoped to what the agent needs, and the tool list follows that key.
Wavix's hosted MCP server. One HTTPS endpoint with an API key in the Authorization header, and the whole account becomes callable: messaging, voice, call records, number purchasing, SIP trunking, verification and billing.
- SMS and MMS: send, retrieve, list and filter messages, manage Sender IDs, and maintain the opt-out list
- Voice: place and answer calls, play and stop audio, collect DTMF, start and stop media streams, and manage call webhooks
- Call records: search CDRs by date, number and disposition, pull recordings and their transcriptions, or request a retranscription
- Speech analytics submitted, retrieved, retranscribed, and the source audio downloaded
- Phone numbers: search by country, region and city, add to a cart and check out, then route, configure, document or release what you own
- SIP trunks created, read, updated and deleted
- 10DLC: brands, vettings, appeals, evidence files, campaigns, and the numbers linked to each campaign
- 2FA over SMS, voice or email — send, resend, verify, cancel — with session and event history
- Number validation one at a time or in bulk, WebRTC tokens for browser calling, trackable short links, and outbound voice campaigns
- Billing and account: transactions, invoices and PDF downloads, profile settings, API keys, and sub-accounts
A Wavix account and an API key, sent as a bearer token in the Authorization header. Which tools appear follows the scopes on that key, so a key scoped to messaging will not surface trunking or number purchasing.
One command plus a key — claude mcp add --transport http wavix https://mcp.wavix.com/mcp \ --header "Authorization: Bearer YOUR_API_KEY", then supply credentials