With this many credential sets, the usual failure is a tool that silently is not there. Asking the server to list its tools and explain each disabled one turns a confusing absence into a sentence about which key you have not set — worth running first. Beyond sending, the unusual coverage is administrative: creating conversation apps, attaching channels, and taking an RCS sender through carrier review are all callable, which most vendor servers leave to the dashboard.
The vendor's own server over the Sinch APIs. Messaging, voice, verification, email, RCS sender registration, WhatsApp templates and number provisioning are all covered, each area authenticated with its own credentials so you enable only what you use.
- send-text-message, send-media-message, send-choice-message and send-location-message across supported channels
- send-template-message and send-whatsapp-template-message for predefined templates, with list-messaging-templates and list-whatsapp-templates to find them
- create-conversation-app, update-conversation-app, delete-conversation-app and list-conversation-apps, plus set-sms-channel-on-app, set-rcs-channel-on-app and set-whatsapp-channel-on-app
- create-webhook, update-webhook, get-webhook, list-webhooks and delete-webhook for inbound events
- number-lookup, start-sms-verification and report-sms-verification for one-time-password flows
- tts-callout, conference-callout, manage-conference-participant, close-conference and get-call-information on the voice side
- send-email, list-email-templates, retrieve-email-info, list-email-events and analytics-metrics through Mailgun
- list-rcs-senders, create-rcs-sender, update-rcs-sender, launch-rcs-sender and the test-number tools for getting an RCS sender through review
- create-whatsapp-template, update-whatsapp-template and the two deletion tools for template lifecycle
- search-for-available-numbers, rent-sinch-virtual-numbers, list-rented-numbers, list-available-regions and release-rented-number
- sinch-mcp-configuration, which lists every tool and says why any disabled one is disabled
A Sinch Build account and Node.js 20.x or 22.x. Credentials are per API: PROJECT_ID, KEY_ID and KEY_SECRET cover Conversation, Numbers, RCS and WhatsApp templates; Verification and Voice each want their own APPLICATION_KEY and APPLICATION_SECRET; email wants MAILGUN_API_KEY. CONVERSATION_REGION defaults to us and also accepts eu and br. Sending SMS may require DEFAULT_SMS_ORIGINATOR depending on the country, location messages need a Google geocoding key, and RCS has to be enabled on your project by Sinch first. Phone numbers go in everywhere in E.164 form. It is a developer preview.
One command plus a key — npx -y @sinch/mcp, then supply credentials