All servers / Messaging / Sinch MCP server
Sinch MCP server
Sinch MCP server
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 0.0.1-beta.7. Package: @sinch/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (10.3 seconds including download)
- Tools offered: 59
- Last published: 2026-10-30
- Weekly downloads (npm): 1,049
- License: Apache-2.0 · Direct dependencies: 9
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
start-sms-verification1 of 1 parameter describedStart an SMS OTP verification for a phone number (E.164). Use when the user wants to *verify* ownership of a number via a one-time code. After success, ask them for the OTP and call report-sms-verification. Do NOT use number-lookup (carrier/line info) or send-text-message (arbitrary SMS content) for phone number ownership verification flows.
report-sms-verification2 of 2 parameters describedReport the received verification code to verify it, using the phone number of the user
number-lookup1 of 1 parameter describedLook up line/carrier information for a phone number (E.164) via Number Lookup — validity, type, and related metadata. Use when the user asks whether a number is valid or what carrier/type it is. Do NOT use this for RCS device feature support (use get-rcs-number-capabilities), SMS verification codes (use start-sms-verification), or searching Sinch virtual numbers to rent (use search-for-available-numbers).
send-text-message6 of 6 parameters describedSend a text message to a contact on the specified channel. The contact can be a phone number in E.164 format, or the identifier for the specified channel.
send-media-message6 of 6 parameters describedSend a media message from URL given in parameter to a contact on the specified channel. The contact can be a phone number in E.164 format, or the identifier for the specified channel. The media must be specified with its URL.
send-location-message6 of 6 parameters describedSend a location message from an address given in parameter to a contact on the specified channel. The contact can be a phone number in E.164 format, or the identifier for the specified channel.
send-choice-message8 of 8 parameters describedSend a choice message to the user. The choice message can contain up to 3 choices if not text or up to 10 message if text only. Each choice can be a call message (phone number + title to display next to it), a location message (latitude / longitude + title to display next to it), a text message or a URL message (the URL to click on + title to display next to it). The contact can be a phone number in E.164 format, or the identifier for the specified channel.
send-template-message8 of 8 parameters describedSend an omni-template message (referred by template ID, ULID) to a contact on the specified channel. The contact can be a phone number in E.164 format, or the identifier for the specified channel.
send-whatsapp-template-message8 of 8 parameters describedSend a WhatsApp-native template message (referred by template name) to a contact (phone number in E.164 format) on the WhatsApp channel. For omni-channel templates use send-template-message instead.
list-conversation-appsno parametersGet a list of all Conversation apps in the account. Apps are created and configured in the Sinch Dashboard or with the Conversation API. The App is the entity that holds the credentials related to the various channels
create-conversation-app2 of 2 parameters describedCreate a new Conversation API app in the project. No channels are configured at creation; use set-sms-channel-on-app, set-rcs-channel-on-app, or set-whatsapp-channel-on-app to configure channels later. Read the conversation-app-setup resource for the full flow.
update-conversation-app3 of 3 parameters describedUpdate a Conversation API app display name. To configure or replace channel credentials, use set-sms-channel-on-app, set-rcs-channel-on-app, or set-whatsapp-channel-on-app instead.
delete-conversation-app2 of 2 parameters describedDelete a Conversation API app by its ID. This permanently removes the app and its channel configuration.
set-sms-channel-on-app4 of 4 parameters describedSet (create or replace) the SMS channel on a Conversation API app. Requires the SMS service plan ID and API token. The app must be in the same region as the SMS service plan. To rename an app, use update-conversation-app instead. For vague requests such as "add messaging", ask whether the user means SMS, RCS, or WhatsApp and collect the required credentials before calling a tool.
set-rcs-channel-on-app4 of 4 parameters describedSet (create or replace) the RCS channel on a Conversation API app. Requires the RCS sender ID and bearer token. To rename an app, use update-conversation-app instead. For vague requests such as "add messaging", ask whether the user means SMS, RCS, or WhatsApp and collect the required credentials before calling a tool.
set-whatsapp-channel-on-app4 of 4 parameters describedSet (create or replace) the WhatsApp channel on a Conversation API app. Requires the WhatsApp sender ID and bearer token. To rename an app, use update-conversation-app instead. For vague requests such as "add messaging", ask whether the user means SMS, RCS, or WhatsApp and collect the required credentials before calling a tool.
list-messaging-templatesno parametersGet a list of the omni-channel messaging templates (managed by Sinch) belonging to an account, for the configured region only. Note that this list does NOT include: (1) Email templates - use the list-email-templates tool to fetch them; (2) WhatsApp channel-specific templates (managed by Meta) - use the list-whatsapp-templates tool to fetch them. If the user asks for all their messaging templates, you can propose to additionally call list-whatsapp-templates to fetch the WhatsApp-specific templates.
list-webhooks2 of 2 parameters describedList all webhooks configured for a Conversation app. Webhooks receive Conversation API callbacks at a target URL when selected triggers occur. Configure signing secrets in the Sinch Dashboard.
get-webhook2 of 2 parameters describedGet a Conversation API webhook by its ID. Signing secrets are not returned — configure them in the Sinch Dashboard. Use list-webhooks to browse webhooks when the user does not have an ID yet.
create-webhook4 of 4 parameters describedCreate a webhook for a Conversation app (up to 5 per app). Events are delivered to the target URL over HTTP when triggers fire. Configure the signing secret in the Sinch Dashboard; it is not set through this tool.
update-webhook4 of 4 parameters describedUpdate an existing Conversation API webhook. Provide at least one of target or triggers. Signing secrets are configured in the Sinch Dashboard, not through this tool.
delete-webhook2 of 2 parameters describedPermanently delete a Conversation API webhook by its ID. Ask for the webhook ID if missing. Prefer update-webhook to clear triggers if the user only wants to disable events.
tts-callout8 of 8 parameters describedPlace an outbound voice call that speaks a text-to-speech message when answered and returns a session ID. A session contains one or more call legs; use get-session-information to retrieve their call IDs and states. Use when the user wants to call a phone number and say something aloud. Do NOT use send-text-message for this. Requires phoneNumber and message; the caller ID is optional.
get-call-information1 of 1 parameter describedGet status and details for one voice call leg by call ID. A call is one leg within a session: use get-session-information first when you have the session ID returned by tts-callout or obtained from a batch. Do not use this to place a call or send an SMS.
list-calls10 of 10 parameters describedList and filter voice call legs by service, endpoints, channel, time range, result, or reason. Results are returned one page at a time with pagination metadata.
get-session-information1 of 1 parameter describedGet voice session details by session ID, including the call IDs and state of every call leg in the session. Sessions are returned directly by tts-callout or as part of a batch. Use get-call-information with a returned call ID to inspect one leg.
create-voice-service3 of 3 parameters describedCreate a Voice service. Optionally add a description or make it the project default.
set-voice-service-webhook3 of 3 parameters describedSet the primary webhook URL and fallback URL for a Voice service. This replaces its current call behavior with webhook handling.
remove-voice-service-webhook1 of 1 parameter describedRemove webhook configuration from a Voice service, leaving it with no incoming-call behavior.
assign-number-to-voice-service2 of 2 parameters describedAssign an active Sinch number to a Voice service. The number must belong to the authenticated project and have Voice capability.
tts-batch-callout10 of 10 parameters describedCreate a batch of outbound voice calls that all play the same text-to-speech message. Accepts 1-500 E.164 destinations and returns a batch ID; each destination creates a session, and each session contains one or more call legs. Use get-voice-batch-summary to retrieve the session IDs for the batch. The caller ID is optional.
get-voice-batch-summary2 of 2 parameters describedGet the execution summary for an outbound voice-call batch by batch ID. Enable session details to return the ID and state of each session in the batch; then use get-session-information to retrieve the call legs in a session.
send-email7 of 7 parameters describedSend an email to a recipient with a subject and body.
retrieve-email-info2 of 2 parameters describedRetrieve the content of an email and the events that happened thanks to its ID
list-email-templates1 of 1 parameter describedGet a list of Email templates from Mailgun for a specific domain. Note that the Messaging templates (omni-channel or channel-specific such as WhatsApp) are NOT included in this list - they can be found with another tool: list-messaging-templates. Do not try to use this tool to list Messaging templates, it will not work.
list-email-events5 of 5 parameters describedGet a raw log of individual email events from Mailgun for a specific domain, not aggregated rates or totals — for those, use analytics-metrics instead. You can filter by event type and limit the number of results.
analytics-metrics4 of 4 parameters describedGet aggregated email analytics from Mailgun for an account, such as rates and counts, computed over a time range. Use this for questions about rates, percentages, or totals. For a raw log of individual email events, use list-email-events instead. All parameters are optional. You can filter by domain, metrics type and specify a time range. By default, it will return all metrics for all your domains for the last 7 days.
list-available-regions1 of 1 parameter describedList countries/regions where Sinch virtual numbers are available to search and rent. Use when the user asks where they can buy numbers or which regions are offered. Optional filter by number types (MOBILE, LOCAL, TOLL_FREE). If the user later wants to find candidates in a region, they can follow up with search-for-available-numbers.
list-rented-numbers6 of 6 parameters describedList phone numbers already rented/active on this project. Optional filters: region, type, digit pattern, SMS/VOICE capability. Use this to see what you own — not to find numbers still available to buy (use search-for-available-numbers) and not to look up carrier/line type for an arbitrary number (use number-lookup).
rent-sinch-virtual-numbers1 of 1 parameter describedRent (activate) one or more known Sinch virtual phone numbers on the project. Requires specific E.164 numbers (with leading +) that the user already chose — typically after search-for-available-numbers. Do NOT invent phone numbers. Do NOT use this to search or browse available numbers — use search-for-available-numbers for that. If the user has not provided an exact number, ask for it or search first.
release-rented-number1 of 1 parameter describedRelease (cancel) a rented virtual phone number from the project. Requires the exact E.164 phone number. Ask for the number if missing. This is not for searching or renting numbers.
get-rented-number-configuration1 of 1 parameter describedGet a rented Sinch number by its exact E.164 phone number, including its metadata, capabilities, and current service configuration. Provisioning updates are asynchronous: while an update is pending, its future configuration and status appear in the corresponding `scheduled*Provisioning` property.
search-for-available-numbers6 of 6 parameters describedSearch for available Sinch virtual phone numbers you can rent (activate) later. Use this when the user wants to find or browse numbers (by country/region, type LOCAL/MOBILE/TOLL_FREE, area-code pattern, or SMS/VOICE capability) but has not yet chosen a specific E.164 number to activate. Do NOT use this to activate/rent a known number — use rent-sinch-virtual-numbers for that. If the user asks vaguely for "a support line" or "a number" without region/type, ask for country/region (and optionally area code or capabilities) before calling, or call this tool once those filters are clear.
list-rcs-senders1 of 1 parameter describedList RCS senders for the project. Returns up to 50 senders per page. Use pageToken for pagination.
get-rcs-sender1 of 1 parameter describedGet an RCS sender by ID. Returns authName and authToken needed for set-rcs-channel-on-app (as senderId and bearerToken respectively), plus state, details, and countryStatus. Note: the sender's `id` field must NOT be used as senderId in set-rcs-channel-on-app — use authName instead.
create-rcs-sender1 of 4 parameters describedCreate an RCS sender. Required fields: region, billingCategory, useCase. You can also pass details (brand, questionnaire, countries) in the same call to fill them upfront, or use update-rcs-sender to add them incrementally — either way, all details must be complete before the sender can be launched.
update-rcs-sender2 of 2 parameters describedUpdate a RCS sender details (brand, countries, testNumbers, questionnaire). billingCategory, useCase, and region cannot be changed after creation.
add-rcs-test-number2 of 2 parameters describedAdd test phone numbers to an RCS sender. Re-adding a verified number resets it to unverified.
delete-rcs-test-number2 of 2 parameters describedDelete a test number from an RCS sender. Use when state is DECLINED, REJECTED, or INVALID before re-adding.
resend-rcs-test-number-invite2 of 2 parameters describedResend a test number invite for an RCS sender. Use when state is PENDING or UNVERIFIED. Resets VERIFIED to UNVERIFIED.
get-rcs-number-capabilities2 of 2 parameters describedReturn RCS features supported by a specific RCS test number device registered on a given RCS agent (supported actions, rich card layouts, revocation). Requires senderId and the test phone number. Use when the user asks whether a tester can receive RCS / which RCS features their device supports. Do NOT use number-lookup for this — that checks carrier/line type, not RCS client capabilities.
get-rcs-test-number-state2 of 2 parameters describedGet the state of one RCS test number (PENDING, VERIFIED, UNVERIFIED, etc.). To see all test numbers at once, use get-rcs-sender.
launch-rcs-sender1 of 1 parameter describedSubmit an RCS sender for Google and carrier review. Before calling this tool, verify ALL of the following are set via update-rcs-sender — the launch is rejected if any item is missing: (1) details.brand.name; (2) details.brand.logoUrl (JPEG/PNG, max 50 KB, 224×224 px); (3) details.brand.bannerUrl (JPEG/PNG, max 200 KB, 1440×448 px); (4) details.brand.privacyPolicyUrl; (5) details.brand.termsOfServiceUrl; (6) at least one of details.brand.phones or details.brand.emails; (7) details.countries with at least one supported country code; (8) details.questionnaire.general.answers — all fields; (9) details.questionnaire.verification.answers — all fields; (10) country-specific questionnaire section for each country in details.countries (e.g. questionnaire.gb for GB, questionnaire.us for US, questionnaire.fr for FR). Use get-rcs-sender to review current values before launching. If the launch is rejected, the response lists exactly which required details are still missing so they can be filled in and the launch retried.
get-whatsapp-accountno parametersGet the WhatsApp Business Account (WABA) for the project: state, WABA ID, business details, ban state and date, daily message limit, compatible regions, and the Insights / Direct Send flags. Note: the Meta quality rating is not part of the response.
list-whatsapp-templatesno parametersGet a list of the WhatsApp channel-specific message templates (submitted to and reviewed by Meta) belonging to a project. Note that the omni-channel messaging templates (managed by Sinch) are NOT included in this list - use the list-messaging-templates tool to fetch them. If the user asks for all their messaging templates, you can combine this tool with list-messaging-templates.
create-whatsapp-template7 of 7 parameters describedCreate a WhatsApp message template in the project. Required fields: name, language, category. Provide details.components to define the content — it must include a BODY component. If status is SUBMIT (the default), the template is submitted for review immediately; if DRAFT, it is saved without validation for later editing.
update-whatsapp-template6 of 6 parameters describedUpdate a DRAFT WhatsApp message template, identified by templateName and languageCode. APPROVED, REJECTED, PAUSED, or DISABLED templates can also be updated, and are reset to draft. Not every field can be changed this way — unsupported changes require deleting the draft and creating a new one.
delete-single-whatsapp-template-language3 of 3 parameters describedDestructive — always ask the user to confirm the exact templateName and languageCode in chat and wait for an explicit yes before calling this tool. Delete ONE language variant of a WhatsApp message template, identified by templateName and languageCode — other language variants of this template name are left untouched. To delete every language variant of a template name at once, use delete-all-whatsapp-template-languages instead. By default only the draft is removed; set deleteSubmitted to also remove a template already submitted to Meta. The template name itself is not freed up by deletion — recreating a template with this same name and language is blocked for 30 days after an approved variant is deleted; update the submitted template instead if you need it again soon.
delete-all-whatsapp-template-languages1 of 1 parameter describedDestructive — always ask the user to confirm the exact templateName in chat and wait for an explicit yes before calling this tool. Delete ALL language variants of a WhatsApp message template by name, in one call — draft and submitted variants alike, regardless of state. This is more destructive than delete-single-whatsapp-template-language, which only removes a single language variant; use this one only when every language of the template name should be removed. This does not free up the name — recreating a template with this same name and any language it had approved is blocked for 30 days. In-flight messages already sent with the deleted template keep attempting delivery for 30 days.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.