{"id":"com.turbonotify/turbo-notify","slug":"com-turbonotify-turbo-notify","title":"Turbo Notify: WhatsApp for AI agents","description":"Send, receive, edit and react to WhatsApp messages from your own number. OAuth or API key sign-in.","version":"1.5.13","publisher":{"kind":"domain","id":"turbonotify.com","label":"turbonotify.com","url":"https://turbonotify.com"},"website":"https://docs.turbonotify.com/en/agents/mcp-server/","repository":"https://github.com/turbo-notify/agent-skills","remotes":[{"type":"streamable-http","url":"https://mcp.turbonotify.com","headers":[{"description":"No account yet? Use Install below: your app opens the Turbo Notify sign-in, where you create your account and link your number. Have an API key? Paste it here as Bearer YOUR_KEY, limited to what you need.","isSecret":true,"name":"Authorization"}]}],"packages":[],"published":"2026-11-13","updated":"2026-11-13","status":"online","auth":"","latency_ms":1262,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"send_text","title":"Send a text message","description":"Send a WhatsApp text message.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\nWriting `@<number>` in the text mentions that person, for example\n`@5511999999999`. The platform detects it automatically; there is no\nseparate mentions argument.\n\nThis is also how to answer the message you just received: a normal\nmessage to its sender, as a person does in a chat, with no quote. Quote","read_only":false},{"name":"send_media","title":"Send an image, video, audio, document or sticker","description":"Send media by URL: an image, video, audio clip, document or sticker.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\n`url` must still be reachable when the send happens: Turbo Notify\nfetches the bytes from it. A copy is kept in the organization's own\nobject storage afterwards when that is configured, which never blocks\nthe send and is not required for one.\n\n`caption` applies to","read_only":false},{"name":"send_location","title":"Send a map location","description":"Send a location pin.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\n`latitude` is between -90 and 90, `longitude` between -180 and 180.\n`name` and `address` label the pin; `url` adds a link beside it.\n\nA location cannot be edited after it is sent: `delete_message` is the\nonly change for it.\n","read_only":false},{"name":"send_contact_card","title":"Send a contact card","description":"Send a contact card the recipient can save to their phone.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\n`phones` takes plain E.164 numbers, 1 to 10 of them. `emails`,\n`organization`, `title` and `address` are optional extra fields on the\ncard; `emails` allows up to 10 as well.\n\nA contact card cannot be edited after it is sent: `delete_message` is the\nonly change for it.\n","read_only":false},{"name":"send_calendar_event","title":"Send a calendar event","description":"Send a calendar event invitation.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\n`start_at` and `end_at` are ISO 8601 **with an offset**, for example\n`2026-09-10T14:00:00Z`. A timestamp without one is rejected: the\nrecipient's phone renders the event in their own timezone, so an\nambiguous instant would show the wrong hour on their screen.\n\nWhen set, `end_at` must be after `sta","read_only":false},{"name":"send_cta_button","title":"Send a message with a call-to-action link button","description":"Send an interactive message carrying one link button.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\nA link button is the only interactive type WhatsApp accepts on this kind\nof connection. Reply buttons and list pickers are not available and will\nnot become available, so do not try to emulate them.\n\n`body` is the text above the button (up to 1024 characters),\n`button_text` its","read_only":false},{"name":"reply_to_message","title":"Reply to a message in the same conversation","description":"Reply to an EARLIER message, quoting it, without naming a recipient.\n\nUse it to bring context into the conversation: when the conversation has\nmoved on and your answer depends on something said a while ago (by the\ncontact, by you or, in a group, by any participant). To answer the\nmessage you just received, do not use this tool: send a normal message\nwith `send_text` and let the chat carry the cont","read_only":false},{"name":"edit_text_message","title":"Edit the text of a message already sent","description":"Replace the text of a text message this number already sent.\n\nThe recipient sees the new text marked as edited. The message keeps its\nid and its place in the conversation; only the text changes.\n\nOnly a text message can be edited here. For the caption of an image,\nvideo or document use `edit_media_caption`, and for a calendar event\n`edit_calendar_event` or `cancel_calendar_event`. A location, cont","read_only":false},{"name":"edit_media_caption","title":"Edit the caption of an image, video or document","description":"Replace the caption of an image, video or document this number already sent.\n\nThe recipient sees the new caption marked as edited. The file itself\nstays exactly as it was and the message keeps its id: only the caption\nchanges. There is no way to replace the file; to send a different one,\nsend a new message with `send_media`.\n\nOnly an image, video or document can be edited this way. Audio and\nstick","read_only":false},{"name":"edit_calendar_event","title":"Edit a calendar event already sent","description":"Correct a calendar event this number already sent.\n\n`name` and `start_at` are always required, plus whatever else the event\nhas: `description`, `end_at`, `join_link`, `location`, `has_reminder`\nwith `reminder_offset_sec`, and `extra_guests_allowed`. This REPLACES the\nwhole event: anything you leave out is removed from it, including its\nlocation, reminder and guest setting, so send again every deta","read_only":false},{"name":"cancel_calendar_event","title":"Cancel a calendar event already sent","description":"Cancel a calendar event this number already sent.\n\nThe event stays in the chat marked as canceled, and WhatsApp tells the\nguests. Send the same `name` and `start_at` the event has, plus the\ndetails you want the canceled card to still show (`description`,\n`end_at`, `join_link`, `location`, `has_reminder` with\n`reminder_offset_sec`, `extra_guests_allowed`): the canceled event is\nshown with what you ","read_only":false},{"name":"delete_message","title":"Delete a message for everyone","description":"Revoke a message for everyone in the conversation.\n\nThis is WhatsApp's \"delete for everyone\". It is not reversible, and\nrecipients see a tombstone where the message was, so they can tell\nsomething was deleted. Confirm with a human before using it on anything\na person has plausibly already read.\n\nThe number first appears online and its unread messages in that\nconversation are marked as read, then t","read_only":false},{"name":"react_to_message","title":"React to a message with an emoji","description":"Attach an emoji reaction to a message, or remove one.\n\nPass a single emoji character, e.g. `👍`. Passing an empty string\nremoves the reaction this number previously left. A new emoji\nreplaces this number's previous reaction rather than adding beside\nit; to bring the earlier one back, react with it again.\n\nWorks on messages in either direction: reacting to something a customer\nsent is often a cheape","read_only":false},{"name":"send_typing_indicator","title":"Show the typing indicator in a conversation","description":"Show \"typing…\" to a recipient while you prepare an answer.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\n\nUseful before a reply that takes a few seconds to compose, so the person\non the other end sees something is happening. It expires on its own, so\nclearing it is optional: pass `is_typing=false` only if you decide not\nto answer after all and want the indicator gone at once.\n","read_only":false},{"name":"mark_as_read","title":"Clear a conversation's unread backlog","description":"Mark a conversation's unread messages as read, without sending anything.\n\nSet exactly one recipient: `number`, `group_id`, or `contact_id`.\nWith `number` or `contact_id`, only the one-to-one chat with that person\nis marked as read: the messages they sent in groups stay unread. For a\ngroup, pass its `group_id`.\n\nThis is independent of the automatic mark-as-read that already happens\nwhen you send, r","read_only":false},{"name":"list_messages","title":"List messages in an inbox","description":"List messages for one number, newest first, received and sent.\n\nEach item says who it is from and to, which number it belongs to, its\n`direction`, `content_type`, `origin`, a short `preview`, `at`, `status`\nand `content_expired`. Mentions, transcription and full media detail\nare only on `get_message`, so fetch the one message you care about\nrather than paging for detail.\n\nTo read a group, find its","read_only":true},{"name":"get_message","title":"Get one message in full","description":"Fetch one message with its full content, parties and mentions.\n\nThe answer includes the number's stable `number_id` (`num_…`) next to\n`number_alias`.\n\n`at` is when the message actually happened on WhatsApp; `status.at` is\nwhen it reached its current delivery status and keeps moving as receipts\narrive. They answer different questions and are not interchangeable.\n\nReturns not found if the id belongs","read_only":true},{"name":"get_message_status","title":"Get a message's delivery status","description":"Check where a message got to: queued, sent, delivered, read, failed.\n\nStatus only moves forward. A failed status always carries an error\ncode, and for a few media and reaction problems it also carries a hint\nnaming the field to change; most failures give the code alone. Read the\ncode before retrying, because most failures repeat identically.\n","read_only":true},{"name":"get_message_receipts","title":"Get per-recipient delivery and read receipts","description":"See who received and who read a message.\n\nMost useful for group messages, where the single status on the message\ncannot express that some members read it and others have not.\n\nRequires a plan that includes read receipts; on plans without it the\ncall is refused with `feature_not_available`, which no retry will fix.\n","read_only":true},{"name":"get_message_reactions","title":"Get the reactions on a message","description":"List the emoji reactions on a message, and who left each one.\n\nEach entry names the reactor and the emoji. Reactions are replaced\nrather than accumulated per person: someone who reacts twice leaves one\nentry showing their latest emoji, so this is a current snapshot and not\na history.\n\nAn empty list is the normal answer for most messages, and is not an\nerror.\n","read_only":true},{"name":"get_message_responses","title":"Get the guests' answers to a calendar event","description":"See how the guests answered a calendar event: going, not going or maybe.\n\nOnly works on a calendar event; any other message answers\n`invalid_request: message_not_calendar`.\n\nThe answer has `counts` (how many guests are going, not going or\nmaybe, and how many extra guests those who are going or maybe are\nbringing) and `responses`, one entry per guest with who they are, their\nanswer, any extra guest","read_only":true},{"name":"get_message_quota","title":"Get a number's message quota for this billing cycle","description":"Check how much of this number's message allowance is left.\n\nThe quota is **per number**, not per organization: an organization with\nthree numbers has three separate allowances. It resets at `cycle_end`,\nwhich is the organization's real billing boundary rather than a rolling\nwindow, so `resets_at` is a date you can plan around.\n\nOnly messages sent through Turbo Notify consume it. Messages someone\ns","read_only":true},{"name":"list_contacts","title":"List an inbox's contacts","description":"List the people this number has exchanged messages with.\n\nFilter by `phone` or by `name`. They are separate filters, not one\nsearch box: `name` matches the contact's name, `phone` matches the\nnumber.\n\n`source` restricts to how the contact first appeared: `inbound` (they\nmessaged this number), `outbound` (this number messaged them),\n`mention` (named in a group message) or `self` (the number's own\nc","read_only":true},{"name":"get_contact","title":"Get one contact","description":"Fetch one contact: name, phone number and activity timestamps.\n\n`first_messaged_at` is when a message from this number first reached\nthem on WhatsApp, and `last_interaction_at` is the last message that\npassed in EITHER direction, so it moves when they write to you as well.\nA message that failed before reaching WhatsApp moves neither.\n\n`refresh` shows the last `refresh_contact` you asked for: when ","read_only":true},{"name":"get_contact_profile_picture","title":"Get a contact's profile picture","description":"Get a contact's profile picture, or the reason there is none.\n\nThe answer carries `kind`: `available` with a temporary URL, or\n`unavailable` with a reason. `no_storage` means the organization has not configured object\nstorage, which is a setup step rather than a fault with this contact.\nThe person may also simply have no picture, or have hidden it in their\nprivacy settings.\n","read_only":true},{"name":"refresh_contact","title":"Refresh a contact's WhatsApp name","description":"Ask WhatsApp for this contact's current name.\n\nOnly the name is refreshed. The profile picture updates on its own the\nnext time this number exchanges a message with the contact, and this\ndoes not change how messages reach them.\n\nIt answers right away with `requested_at`; the refresh then runs in the\nbackground. Call `get_contact` and read `refresh`: when `completed_at`\nis set, `outcome` says what ","read_only":false},{"name":"get_contact_quota","title":"Get a number's contact quota for this billing cycle","description":"Check how much of this number's contact allowance is left.\n\nA contact counts once per billing cycle when this number messages them\nthrough Turbo Notify, new **or** returning. Messaging the same person\nagain in a later cycle counts again.\n\nLike the message quota, this is per number rather than per organization,\nand it resets at `cycle_end`.\n","read_only":true},{"name":"list_groups","title":"List the groups a number belongs to","description":"List the WhatsApp groups this number is a member of.\n\nThe list is built when the number connects: every group it belongs to\nis picked up then, whether or not anything has been said in it. A group\njoined since then is picked up from the join itself, without waiting\nfor anyone to speak in it.\n\n`name` filters by group name. `include_left=true` also returns groups\nthis number has left, which are other","read_only":true},{"name":"get_group","title":"Get one group","description":"Fetch a group: its name, description, picture and settings.\n\nReturns how many participants it has, not who they are. Membership is\ndeliberately not readable: it arrives as it changes, on the\n`group.participants_added` / `_removed` / `_promoted` / `_demoted`\nevents, which `list_events` can read.\n","read_only":true},{"name":"get_group_picture","title":"Get a group's picture","description":"Get a group's picture, or the reason there is none.\n\nSame shape as a contact's picture. The answer carries `kind`:\n`available` with a temporary URL, or `unavailable` with a reason. `no_storage` means the organization has not\nconfigured object storage.\n","read_only":true},{"name":"list_numbers","title":"List the organization's WhatsApp numbers","description":"List every WhatsApp number this organization has, with its status.\n\nStart here when you do not know which aliases exist. The main number is\nalways `main`; extras carry the alias the customer chose, and that alias\nis what every other tool's `number_alias` expects.\n\nEach number also carries `id` (`num_…`), which never changes, even when\nthe alias is renamed. Keep it if you need to recognise a number","read_only":true},{"name":"get_number","title":"Get one number and its connection status","description":"Check one number: its phone number, status, and when that status began.\n\n`id` (`num_…`) is the number's permanent identifier. The alias can be\nrenamed, the `id` cannot. Either one works as `number_alias`.\n\n`connected` means it can send right now. `connecting` means a connection\nwas just requested and is being set up; check again in a few seconds.\n`reconnecting` means the number lost its connection","read_only":true},{"name":"connect_number","title":"Bring a number back online","description":"Reconnect a number that is currently offline.\n\nUses the credentials already stored for the number, so no QR code and no\nhuman are involved. Use it when `get_number` reports `disconnected` and\nyou want to send.\n\nReturns immediately, before the connection is established. The answer\nhas the number's `alias`, `status` set to `connecting` and `at`, the\nmoment the request was accepted. The number reache","read_only":false},{"name":"disconnect_number","title":"Take a number offline without unlinking it","description":"Take a number offline deliberately, keeping its link to the phone.\n\nThe stored credentials survive, so `connect_number` brings it straight\nback with no pairing. Nothing is deleted. Disconnecting does not stop billing:\nan extra number is billed every cycle until it is removed.\n\nReturns immediately, before the number is offline. The answer has the\nnumber's `alias`, `status` set to `disconnecting` an","read_only":false},{"name":"get_usage","title":"Get the organization's usage across all numbers","description":"Get message and contact usage for the whole organization.\n\nThe top-level totals are the **sum across every live number**: an\norganization with two numbers on a 50,000-message plan reports a quota\nof 100,000, not 50,000. The `numbers[]` breakdown shows each number\nseparately, which is what you need to find the one that is close to its\nown ceiling, so a healthy-looking total can hide a number at 99%","read_only":true},{"name":"list_events","title":"Poll the organization's event log","description":"Poll everything that happened: messages, contacts, groups, numbers, quotas.\n\nThis is how an agent learns about inbound messages without hosting a\nwebhook endpoint.\n\n**Events come back newest first, so polling for new ones uses\n`ending_before`, not `starting_after`.** Typical loop: call with no\ncursor and remember the id of the FIRST event in the page (the newest\none); next time, pass that id as `e","read_only":true}],"server_info":{"description":"Send and receive WhatsApp messages through Turbo Notify.","icons":[{"mimeType":"image/png","sizes":["512x512"],"src":"https://mcp.turbonotify.com/icon.png"},{"mimeType":"image/svg+xml","sizes":["any"],"src":"https://mcp.turbonotify.com/favicon.svg"}],"name":"turbo-notify","title":"Turbo Notify","version":"1.5.13","websiteUrl":"https://turbonotify.com"},"category":"communication","tags":["productivity","agents","image-video"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-06","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/com-turbonotify-turbo-notify/"}