SMS, WhatsApp and RCS each have their own send and report tools, so a campaign can be launched and then measured in the same conversation. Authentication is a username and password passed through login_to_telinfy rather than a key you paste into a config file — decide where this server runs before you connect it.
A hosted server over Telinfy's messaging platform, reached over SSE. It covers sending, scheduling, contact lists and campaign reporting across three channels.
- send_sms with DLT compliance, schedule_sms for a future send, scheduleDynamicCampaign for a campaign driven by an Excel file and template variables
- get_sms_schedule for what is queued, fetch_sms_campaign_report for how a campaign performed
- send_whatsapp_campaign using pre-created templates, whatsapp_campaign to list campaigns, fetch_whatsapp_smart_report for reports with date filtering
- fetch_rcs_report for RCS message reports, also date-filtered
- create_phonebook, get_phonebook_groups, get_group_contacts, edit_contact, toggle_contact_status and delete_contact_group for contact lists
- getMessageReport for delivery status on messages already sent
- login_to_telinfy to authenticate and open a session
A Telinfy username and password — login_to_telinfy establishes the session and retrieves the API credentials from them. The endpoint is https://mcp.telinfy.com/sse, over SSE.
One command plus a key — claude mcp add -s user -t http telinfy https://mcp.telinfy.com/sse, then supply credentials