Connect Claude to the Telinfy messaging platform β send SMS and WhatsApp campaigns, manage phonebooks, and pull delivery reports through natural language.
The Telinfy connector is a remote Model Context Protocol (MCP) server operated by Telinfy. Once you connect it to Claude, you can ask Claude in plain language to:
Claude only ever acts on your Telinfy account, using access you grant through Telinfy's own sign-in β and every send uses the sender IDs and message templates already registered and approved on your account.
Telinfy is GreenAds Global's messaging platform. New to the idea? See the AI messaging campaigns overview and the WhatsApp MCP server announcement for the product story and pricing β this page is the technical reference for the connector itself.
https://mcp.telinfy.com
claude mcp add --transport http telinfy https://mcp.telinfy.com
Claude Code will walk you through the same Telinfy sign-in in your browser the first time a tool is used.
Add to Cursor (opens Cursor and adds the server), or add it
to ~/.cursor/mcp.json yourself:
{
"mcpServers": {
"telinfy": { "url": "https://mcp.telinfy.com" }
}
}
Cursor shows a Needs login button next to the server; click it to sign in with your Telinfy username and password. The same tools, consent rules and sign-in apply as in Claude.
The connector uses the standard OAuth 2.0 authorization-code flow with PKCE:
https://mcp.telinfy.com/authorize.To disconnect at any time, remove the connector in Settings β Connectors. Access
tokens expire automatically after 8 hours and can be revoked immediately via the connector's
/revoke endpoint.
sn / senderName.template_id.
The message text you send must match the registered template (variables allowed only where
the template defines them).template_name. Free-form WhatsApp messages are not supported.send_sms, schedule_sms and send_whatsapp_campaign verify every
recipient against your Telinfy phonebook and refuse any number that is not a saved, active
contact. Manage your consented audience with the phonebook tools β deactivating a contact records
their opt-out and immediately excludes them from new sends and schedules. A campaign that was
already scheduled before the opt-out is executed by the platform as queued.These are the tools Claude can call on your behalf. read-only tools only fetch data; write tools send messages or change your account data, and Claude asks for your confirmation before using them.
| Tool | What it does | Key inputs |
|---|---|---|
send_sms write |
Send an SMS campaign immediately. Recipients must be saved, active phonebook contacts. | campName, RType (0 promotional / 1 transactional),
sn, msg, mnos, template_id |
schedule_sms write |
Schedule an SMS campaign for a future time. Recipients must be saved, active phonebook contacts. | Same as send_sms plus execTime
(YYYY-MM-DD HH:mm:ss) |
fetch_sms_campaign_report read-only |
Delivery report for one campaign. | cid (campaign ID) |
get_sms_schedule read-only |
List scheduled SMS campaigns. | β |
getMessageReport read-only |
Delivery status of sent messages. | β |
Dynamic Excel-based campaigns are currently available only in the Telinfy web portal; they will return to the connector once recipient consent checks for spreadsheet campaigns are in place.
| Tool | What it does | Key inputs |
|---|---|---|
send_whatsapp_campaign write |
Send a WhatsApp campaign from an approved template. Recipients must be saved, active phonebook contacts. | campaign_name, numbers, template_name, optional
components, number_type |
whatsapp_campaign read-only |
List your WhatsApp campaigns. | β |
fetch_whatsapp_smart_report read-only |
WhatsApp smart delivery report for a date range. | frmDate, toDate |
| Tool | What it does | Key inputs |
|---|---|---|
fetch_rcs_report read-only |
RCS delivery report for a date range. | frmDate, toDate |
| Tool | What it does | Key inputs |
|---|---|---|
create_phonebook write |
Create a contact group with contacts. | groupName, contacts (first name, last name, phone) |
get_phonebook_groups read-only |
List your contact groups (with group IDs). | β |
get_group_contacts read-only |
List the contacts in a group. | groupID |
edit_contact write |
Update a contact's name or phone number. | contactID, name, phone |
toggle_contact_status write |
Activate or deactivate (opt out) a contact. | groupID, phoneNumber, status (1 active / 0
inactive) |
delete_contact_group write |
Permanently delete a group and all its contacts. | groupID |
| Symptom | Cause & fix |
|---|---|
| "Unauthorized. Please reconnect your Telinfy account." | Your access token has expired (sessions last up to 8 hours, or until your Telinfy sign-in session ends) or was revoked. Reconnect the connector in Settings β Connectors (or re-authenticate when Claude Code prompts you). |
| Sign-in fails with correct credentials | Complete the reCAPTCHA before submitting. If it keeps failing, verify you can sign in at the Telinfy portal with the same credentials β your account may be locked or inactive. |
| "Invalid redirect URI" during sign-in | For security, sign-in only works when it's started from Claude (claude.ai / claude.com) or Cursor. Start the connection from your assistant's connector settings rather than opening the sign-in page directly. |
| "Cannot send: these numbers are not saved, active contactsβ¦" | Sends only reach your opted-in phonebook contacts. Add the numbers to a phonebook group
first (ask Claude to use create_phonebook), or reactivate a deactivated
contact with toggle_contact_status, then retry. |
| SMS send fails or is rejected | The sender ID (sn) and template_id must be DLT-registered and
approved, and the message text must match the registered template. Check them in your
Telinfy portal. |
| Scheduled campaign didn't run | Verify the time was given as YYYY-MM-DD HH:mm:ss in IST and
is in the future (the connector rejects past times). Use
get_sms_schedule to confirm the campaign was registered. |
| "Rate limit exceeded" (HTTP 429) | The server applies per-IP rate limits (e.g. 120 requests/minute on tool calls). Wait a minute and try again. |
| Not sure which URL to enter | Use https://mcp.telinfy.com as the connector URL. Older guides may show
https://mcp.telinfy.com/sse β if that doesn't connect, use the plain URL above. |
| Connector shows no tools / server unreachable | Check https://mcp.telinfy.com/health β it returns OK when
the connector and the Telinfy platform are up. If it doesn't, wait a few minutes or
contact support. |
MCP endpoint (Streamable HTTP): https://mcp.telinfy.com/mcp Β· OAuth discovery:
/.well-known/oauth-authorization-server and
/.well-known/oauth-protected-resource Β· Health: https://mcp.telinfy.com/health
Questions, onboarding help, or something not working? Email support@telinfy.com β include the approximate time and the error message shown in Claude, and we'll take it from there.