Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cosend

REMOTE · MCP.COSEND.APP

WhatsApp Business inbox for AI apps: read and answer chats, run campaigns, deploy automations.

Available components

+2 this week 84 Trust /100

Last scanned (20 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 30302 tokens (~242/item across 125 items; 125 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability check failed: schema churn in the 18 days we've observed: 2 tool removals, 1 breaking changes, 0 auth/transport breaks, 102 additions. See how to fix → Fail
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
  • Structured output schemas are declared (1% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 126 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 46 to 50.

  • 20 Nov 26 0
    • Tool “rollback_automation” rewrote its description, which is the text the model reads security
    • Tool “switch_on_automation” rewrote its description, which is the text the model reads security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.

  • 18 Nov 26 0
    • Tool “get_inbox_overview” rewrote its description, which is the text the model reads security
    • “update_contact” reworded the description of “attributes” cosmetic
    • “upsert_contact” reworded the description of “attributes” cosmetic
  • 17 Nov 26 −1
    • Stability: 0.43 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “automation_recipes” was removed ▼ security
    • Tool “describe_automation” was removed ▼ security
    • Tool “draft_reply” was removed ▼ security
    • Tool “get_authoring_chat” was removed ▼ security
    • Tool “get_automation_catalogue” was removed ▼ security
    • Tool “manage_automation” was removed ▼ security
    • Tool “set_automation_state” was removed ▼ security
    • Tool “translate_message” was removed ▼ security
    • Tool “upsert_automation” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “buy_cosend_number”, which the server declares destructive security
    • New tool “copy_automation”, which the server declares destructive security
    • New tool “create_custom_automation”, which the server declares destructive security
    • New tool “delete_automation”, which the server declares destructive security
    • New tool “keep_cosend_number”, which the server declares destructive security
    • New tool “rollback_automation”, which the server declares destructive security
    • New tool “set_up_accurate_warehouse_arrival”, which the server declares destructive security
    • New tool “set_up_ai_receptionist”, which the server declares destructive security
    • New tool “set_up_appointment_reminder”, which the server declares destructive security
    • New tool “set_up_lead_capture”, which the server declares destructive security
    • New tool “set_up_missed_call_text_back”, which the server declares destructive security
    • New tool “set_up_order_confirmation”, which the server declares destructive security
    • New tool “set_up_order_updates”, which the server declares destructive security
    • New tool “set_up_payment_reminder”, which the server declares destructive security
    • New tool “set_up_quote_intake”, which the server declares destructive security
    • New tool “set_up_review_request”, which the server declares destructive security
    • New tool “set_up_welcome_menu”, which the server declares destructive security
    • New tool “stop_cosend_number”, which the server declares destructive security
    • New tool “switch_off_automation”, which the server declares destructive security
    • New tool “switch_on_automation”, which the server declares destructive security
    • New tool “update_accurate_warehouse_arrival”, which the server declares destructive security
    • New tool “update_ai_receptionist”, which the server declares destructive security
    • New tool “update_appointment_reminder”, which the server declares destructive security
    • New tool “update_automation_details”, which the server declares destructive security
    • New tool “update_custom_automation”, which the server declares destructive security
    • New tool “update_lead_capture”, which the server declares destructive security
    • New tool “update_missed_call_text_back”, which the server declares destructive security
    • New tool “update_order_confirmation”, which the server declares destructive security
    • New tool “update_order_updates”, which the server declares destructive security
    • New tool “update_payment_reminder”, which the server declares destructive security
    • New tool “update_quote_intake”, which the server declares destructive security
    • New tool “update_review_request”, which the server declares destructive security
    • New tool “update_welcome_menu”, which the server declares destructive security
    • Tool “deploy_automation” rewrote its description, which is the text the model reads security
    • Tool “get_report” rewrote its description, which is the text the model reads security
    • Tool “import_contacts” rewrote its description, which is the text the model reads security
    • Tool “manage_number” rewrote its description, which is the text the model reads security
    • Tool “run_automation” rewrote its description, which is the text the model reads security
    • Tool “send_campaign” rewrote its description, which is the text the model reads security
    • Tool “update_campaign” rewrote its description, which is the text the model reads security
    • Schema quality: 215 → 241 ▼ functional
    • “deploy_automation” added a required parameter “actions”, so existing callers break ▼ functional
    • “run_automation” added a required parameter “actions”, so existing callers break ▼ functional
    • First check of Tool coverage: 1 functional
    • New tool “list_automation_building_blocks” functional
    • New tool “list_automation_recipes” functional
    • New tool “list_cosend_numbers” functional
    • “import_contacts” added an optional parameter “details” cosmetic
    • “import_contacts” added an optional parameter “new_fields” cosmetic
    • “update_campaign” added an optional parameter “ab” cosmetic
    • “update_campaign” added an optional parameter “buttons” cosmetic
    • “update_campaign” added an optional parameter “cards” cosmetic
    • “update_campaign” added an optional parameter “header” cosmetic
    • “update_campaign” added an optional parameter “kind” cosmetic
    • “update_campaign” added an optional parameter “let_join” cosmetic
    • “update_campaign” added an optional parameter “reply_rules” cosmetic
    • “update_campaign” added an optional parameter “steps” cosmetic
    • “update_campaign” added an optional parameter “track_clicks” cosmetic
    • “get_report” reworded the description of “card” cosmetic
    • “manage_number” reworded the description of “action” cosmetic
  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.cosend.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.cosend.app CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 e6d88c9d95117b110e3d3f2b21818bf1
SANs: mcp.cosend.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.cosend.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
cosend.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.cosend.app/.well-known/oauth-protected-resource/mcp", scope="messages:read messages:write contacts:read contacts:write templates:read templates:write automations:read automations:write runs:read runs:write connectors:read connectors:write usage:read members:read billing:read settings:read connections:read connections:write approvals:read approvals:write campaigns:read campaigns:write"

Bearer resource_metadata="https://mcp.cosend.app/.well-known/oauth-protected-resource/mcp", scope="messages:read messages:write contacts:read contacts:write templates:read templates:write automations:read automations:write runs:read runs:write connectors:read connectors:write usage:read members:read billing:read settings:read connections:read connections:write approvals:read approvals:write campaigns:read campaigns:write"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Document https://mcp.cosend.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.cosend.app/mcp
Authorisation server https://auth.cosend.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cosend.app/mcp Verified 200
http (plaintext) http://mcp.cosend.app/mcp HTTPS enforced 301 https://mcp.cosend.app/mcp
MCP tools · 125 exposed · ~29,877 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_chat_notes ~133

Lists the internal notes on one conversation, named by id, one page at a time, oldest first: each note’s body, its author, the members it mentions and when it was written or edited. The customer does not see notes. Notes can quote customers and come back marked untrusted. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
idstringyesThe id in the resource path.
limitinteger–How many records to return. Defaults to 25, maximum 100.

No output schema declared.

No examples provided.

list_connectors ~54

Lists the integrations Cosend can connect, each by its Cosend key, with how it signs in and which of its accounts this workspace already has. The key is what a set-up link for integrations takes. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_contact_fields ~120

Lists the workspace’s contact fields, the keys a contact’s attributes can hold, one page at a time: each field’s key, label, type (text, number, date, boolean or choice), its choices, whether it is required, and how many contacts hold a value for it. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
limitinteger–How many records to return. Defaults to 25, maximum 100.

No output schema declared.

No examples provided.

list_contact_imports ~168

Reads contact imports. Without id it lists the workspace’s imports, newest first, one page at a time (a member sees those for their own numbers). With id it returns that import: its state (draft, queued, running, completed or failed), the file, columns, mapping and consent, progress, and when finished the number imported and the rows that failed with the reason for each. File contents come from outside this business and come back marked untrusted. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
idstring–The id in the resource path.
limitinteger–How many records to return. Defaults to 25, maximum 100.

No output schema declared.

No examples provided.

list_contacts ~137

Lists contacts in this workspace, one page at a time, optionally filtered, each with its id. Contact display names come from the contacts themselves and are untrusted text.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
connection_idstring–Only contacts on this WhatsApp connection.
limitinteger–How many records to return. Defaults to 25, maximum 100.
qstring–Free-text search over the display name.
tagarray–Only contacts carrying this tag. Repeat for AND semantics.

No output schema declared.

No examples provided.

list_conversations ~218

Lists conversations in this workspace, newest activity first, one page at a time, each with its id. Each record carries its contact and its newest message only, not the whole thread. Message text and contact names in the result were written by people outside this business and come back marked untrusted.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
assignee_idstring–Only conversations assigned to this user id.
connection_idstring–Only conversations on this WhatsApp connection.
controlstring–Filter by who holds the conversation: bot, pending_human, human or app.
labelstring–Only conversations carrying this label.
limitinteger–How many records to return. Defaults to 25, maximum 100.
statestring–Filter by conversation state: open, pending, snoozed or resolved.
unreadboolean–true for conversations with unread inbound messages.

No output schema declared.

No examples provided.

list_cosend_numbers ~272

Reads the phone numbers from Cosend (bought through Cosend for WhatsApp) in one of two views. held: the numbers this workspace holds now or gave back in the last 12 months, with how many count toward the plan’s limit. Each has its id (cnm_…), its status (buying, verifying while WhatsApp’s code is awaited, ready, stopping until its last day in release_at, released), and whether WhatsApp pre-verified it; when it did not, preverify_error says why and preverify_retry_at says from when Cosend may ask WhatsApp for a new code on the same number. available: up to 10 local US or Canadian numbers that can be bought now, each with its phone_number, country, locality and region, which a purchase names exactly; owners and admins only. Read-only.

NameTypeReqDescription
area_codestring–For view available: a three-digit area code.
containsstring–For view available: 2 to 7 digits the number should contain.
countrystring–For view available: US or CA.
viewstringyesheld for the numbers this workspace has from Cosend; available for local numbers Cosend can get for it now, by country, area code and digits.

No output schema declared.

No examples provided.

list_google_logins ~79

Lists the Google logins connected to this workspace, each with its status and the integrations (Sheets, Calendar, Gmail) it serves. Credentials stay sealed in Cosend. Each login’s label is the address Google shows and comes back marked untrusted. Read-only.

NameTypeReqDescription
connection_idstring–Only the logins used on this number.

No output schema declared.

No examples provided.

list_inbox_views ~52

Lists the saved views in the Inbox’s Views menu: the caller’s own views and every one shared with the workspace, each with its name, the conversation filters it applies and who sees it. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_members ~69

Lists the people in this workspace and its pending invitations, each with role, status and email, and what the next seat costs. Names are typed by the people themselves and come back marked untrusted. Read-only.

NameTypeReqDescription
connection_idstring–Only the people who can see this WhatsApp number.

No output schema declared.

No examples provided.

list_numbers ~137

Lists the WhatsApp numbers connected to this workspace, one page at a time, each with its id, status and health at a glance. The number ids it returns are what other tools take as connection_id. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
limitinteger–How many records to return. Defaults to 25, maximum 100.
modestring–Only numbers connected this way: coexistence or cloud_api.
statusstring–Only numbers in this state, e.g. active.

No output schema declared.

No examples provided.

list_runs ~131

Lists automation runs, newest first, one page at a time, with each run’s status, how long it took and what it sent. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
automation_idstring–Only runs of this automation.
limitinteger–How many records to return. Defaults to 25, maximum 100.
statusstring–Only runs in this state: queued, running, waiting, success, failure, cancelled, timeout, skipped or unknown.

No output schema declared.

No examples provided.

list_template_category_changes ~51

Meta sometimes moves a template to another category, which changes its price. Lists every such change Meta made or announced that nobody in the workspace has acknowledged, on the numbers the caller can see. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_templates ~193

Lists this workspace’s WhatsApp message templates, one page at a time, with Meta’s review status, whether each can be sent right now (sendable) and, for a rejected one, Meta’s reason. Outside the 24-hour customer service window only an approved template can be sent. Meta reviews every template, and a decision can take up to 24 hours, so one in review cannot be sent. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
categorystring–Only this category: marketing, utility or authentication.
languagestring–Only this language, e.g. en_US.
limitinteger–How many records to return. Defaults to 25, maximum 100.
statusstring–Only templates in this review state, e.g. approved.

No output schema declared.

No examples provided.

manage_integration ~319

Manages one connected integration account, named by id; the account returns no credential. action update takes name and config (the account’s non-secret settings). action test makes one safe read at the provider and returns whether the credential works; a failed test is an answer with ok false. action add_number (connection_id) uses the account on another WhatsApp number of the workspace, the same sign-in and not a copy. action remove_number (connection_id) stops using the account on one number, provided the account stays on at least one other number and no switched-on automation there needs it, on a confirmed call: without confirmation_token the call is a preview that returns what would happen and a token for a person to approve. Signing in, and typing or replacing a key, happen on a set-up link the person opens; deleting an account or its saved login is done by a person in the Cosend dashboard. Owners and admins.

NameTypeReqDescription
actionstringyesupdate renames the account or changes its non-secret config. test verifies the credential. add_number and remove_number choose the WhatsApp numbers the account serves.
configobject––
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstring–The connection_id in the resource path.
idstringyesThe id in the resource path.
namestring––

No output schema declared.

No examples provided.

manage_number ~241

Looks after one WhatsApp number, named by id. action sync refreshes the number’s state, quality rating and limits from Meta and returns the connection. action recheck_payment is for a person who added a payment method in Meta after a number was blocked for payment: it asks Meta again and returns the connection (adding the method itself happens in Meta’s own tools). action retry_verification takes the id of a phone number from Cosend (cnm_…) whose verification stopped, and asks WhatsApp for a new code on that same number, with no new purchase; it is allowed from the number’s preverify_retry_at, and the number shows verifying while Cosend waits up to 10 minutes for the code. Owners and admins for sync and retry_verification. Disconnecting a number is an owner’s or admin’s step in the Cosend dashboard.

NameTypeReqDescription
actionstringyessync reads the number’s state from Meta. recheck_payment asks Meta again after a payment method was added. retry_verification asks WhatsApp again for the code that verifies a phone number from Cosend.
idstringyesThe id in the resource path.

No output schema declared.

No examples provided.

mark_read ~172

Marks read, in one of three ways, with id naming a conversation (cosend, phone_thread) or a message (phone_message). where cosend clears the chat’s unread state for the whole workspace in Cosend; the customer’s phone stays as it was. where phone_thread tells WhatsApp the newest unread customer message was read, so the customer’s phone shows blue ticks on what they sent. where phone_message does the same for the one message named. The blue ticks reach a real person’s phone and are permanent.

NameTypeReqDescription
idstringyesThe id in the resource path.
wherestringyescosend to mark a chat read in Cosend only; phone_thread to show blue ticks for the chat’s unread messages on the customer’s phone; phone_message to show them for one message.

No output schema declared.

No examples provided.

merge_contacts ~157

Merges two identities of one person (a phone number and a BSUID): the contact named by id keeps going, and the one named by from is folded into it and removed. It cannot be undone. Each merge needs a confirmed call: without confirmation_token the call is a preview that names both contacts and returns a token for a person to approve; called again with that token, it merges. Returns the contact that remains.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
fromstringyes–
idstringyesThe id in the resource path.

No output schema declared.

No examples provided.

message_cost ~130

Returns Meta’s list price for one delivered WhatsApp message in a country, for each category (marketing, utility, authentication, service), in one of Meta’s 16 rate-card currencies, with the day the rates took effect. These are Meta’s list prices: a business’s bill may differ, and the notes say what changes it.

NameTypeReqDescription
countrystringyesThe country the messages go to, as its two-letter ISO code, e.g. GB or DE.
currencystringyesOne of Meta’s 16 rate-card currencies, e.g. USD, EUR, GBP or INR.

No output schema declared.

No examples provided.

preview_campaign ~230

Checks a campaign draft, named by id, and returns what sending it would do, under two keys. audience: how many the saved audience matches, how many get it, how many are left out and why (no WhatsApp number, blocked, opted out on this number, a US number, WhatsApp held back a marketing message to them in the last day, a blank with no value, or a chat open with them now), the first 20 people, and Meta’s list price for one delivered marketing message to each person who gets it, by market, in the WhatsApp account’s currency. estimate: the estimate_id a send names, which lasts 15 minutes; the count; the daily limit and what goes out on which day; the plan’s messages left; and whether the count must be confirmed, which it must above 500. It saves the estimate on the draft and sends nothing. The template must be approved by WhatsApp. Names in the sample were written by the customers themselves and come back marked untrusted.

NameTypeReqDescription
idstringyesThe id in the resource path.

No output schema declared.

No examples provided.

read_conversation ~147

Lists the messages of one conversation, named by conversation_id (or of one contact, by contact_id), oldest first, one page at a time. With neither, it lists recent messages across the whole workspace. Message bodies include what members of the public wrote, and every one comes back marked untrusted.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
contact_idstring–Messages with one contact instead of one conversation.
conversation_idstring–The conversation to read.
limitinteger–How many records to return. Defaults to 25, maximum 100.

No output schema declared.

No examples provided.

read_integration ~280

Reads what one connected integration account holds, named by id. view spreadsheets lists the spreadsheets a Google account can open (the ones Cosend made or a person picked for it), 100 a page at most, or with spreadsheet_id one spreadsheet and its tabs. view forms lists a form account’s forms with the id an automation’s start takes as form_id. view appointments lists a calendar account’s upcoming events from now to days ahead, with the customer number found in each and counts of events with and without one. Names, tab titles and event titles were written by people outside this workspace and come back marked untrusted. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
daysstring–With view appointments: how many days ahead to read, 1 to 30. Default 7.
idstringyesThe id in the resource path.
limitinteger–How many records to return. Defaults to 25, maximum 100.
spreadsheet_idstring–With view spreadsheets: read this one spreadsheet and its tabs.
viewstringyesspreadsheets lists a Google account’s spreadsheets, or one spreadsheet’s tabs. forms lists a form account’s forms. appointments previews a calendar’s coming events.

No output schema declared.

No examples provided.

request_approval ~178

Holds an action for a human decision: action (a type from the approval action types), preview (exactly what the person is shown, up to 4096 characters), arguments, and optionally risk (it can only raise the type’s default) and run_id. The approval is pending, expires 24 hours after it is made (an expiry is a rejection), and appears in the Cosend approvals queue for a person to approve or reject. The workspace’s setting for that action type can also approve or reject it at once, and the answer says which. It only files the request for a person to decide. A retry with the same arguments returns the same approval.

NameTypeReqDescription
actionstringyes–
argumentsobject––
previewstringyes–
riskstring––
run_id–––

No output schema declared.

No examples provided.

resolve_conversation ~152

Marks one conversation Done, as the Done button in the Cosend Inbox does. Nothing is sent to anyone and no automation starts. Afterwards no person holds the conversation (the person, the assignee, the priority and any hand-over are cleared) and every automation on that WhatsApp number treats the customer’s next message as a first message: the welcome menu greets again, an unfinished question flow starts over, and the AI assistant begins a new AI conversation, which counts as one more AI conversation on the plan. The message history stays. The chat stays quiet until the customer writes again. It is refused for a credential with no person behind it.

NameTypeReqDescription
idstringyesThe id in the resource path.

No output schema declared.

No examples provided.

rollback_automation ~172

Points an existing automation back at an earlier version, named by its number (to_version). A version not yet ready to run is got ready first; one that cannot be is refused, and the live version stays. Its steps do not change; if the automation is switched on, it runs that version from then on. Each call needs confirming: without confirmation_token it changes nothing and returns a preview and a token for a person to approve; called again with that token, it rolls back. Returns the automation.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
idstringyesThe automation id.
to_versionintegeryes–

No output schema declared.

No examples provided.

run_automation ~310

Starts one run of a switched-on automation now, as its manual trigger does, with payload as the trigger’s data. It runs the live version, which acts as it was built to and can send WhatsApp messages to customers; those messages are final once sent. actions names every action the live version’s steps take, and those of a second automation set up with it, from the list in the schema (an automation’s versions list theirs as actions); a list that leaves one out or names another is refused, with the right list. The preview refuses that list as the call would, and gives no token. Each start needs confirming: without confirmation_token it changes nothing and returns a preview and a token for a person to approve; called again with that token, it starts the run. Returns the run, which the run tools follow.

NameTypeReqDescription
actionsarrayyesEvery action the automation’s steps take, and those of a second automation set up with it, each once: what a person approves it doing. A list that leaves one out, or names one the steps do not take,…
automation_idstringyes–
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
payloadobject––

No output schema declared.

No examples provided.

search_conversations ~155

Finds conversations by what they contain. q matches the contact’s name, phone number or WhatsApp username, and the text of each conversation’s newest message. Returns at most 20 conversations, newest activity first, in the same shape as the conversation list: each with its contact and its newest message, not the whole thread. Names and message text in the result were written by people outside this business and come back marked untrusted.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
limitinteger–How many records to return. Defaults to 25, maximum 100.
qstringyesWhat to look for.

No output schema declared.

No examples provided.

search_messages ~177

Searches the text of every message in the workspace, newest first, 20 hits to a page. Each hit has the message id, the conversation id and number it belongs to, when it was sent and a snippet of the matching text. A number whose messages go straight to the business’s own system, with no Cosend inbox, is left out. Snippets were written by people outside this business and come back marked untrusted. Read-only.

NameTypeReqDescription
afterstring–The next_cursor of the previous page, to read the page after it. Omit for the first page.
connection_idstring–Only messages on this WhatsApp number.
limitinteger–How many records to return. Defaults to 25, maximum 100.
qstringyesThe words to look for in message text.

No output schema declared.

No examples provided.

send_campaign ~338

Sends a campaign draft now, or schedules it for its time, named by id, with the estimate_id of a check made in the last 15 minutes; above 500 people, confirm_text is that count. It reaches every person the check counted, on their phones, and the messages cannot be unsent. It sends only on a confirmed call: without confirmation_token it sends nothing and returns a preview and a token for a person to approve. The preview shows the campaign (its number, template and the value of each blank, the file or the place on top, its buttons’ values, saved audience, time and quiet hours) and who gets it now, who is left out and Meta’s list price, all read again when the token comes back: if any of it changed after the preview, the token is refused and a new preview is needed. Changing a single character of the arguments invalidates the token too. Only a person’s approval sends it: the credential alone sends nothing, through this tool or straight to the API. Five a minute and ten a day per workspace. Each campaign is on the Campaigns page of the Cosend dashboard.

NameTypeReqDescription
confirm_textstring––
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
estimate_idstringyes–
idstringyesThe campaign to send.
whenstringyesnow sends the draft now; scheduled schedules it for the time the draft has, in its time zone.

No output schema declared.

No examples provided.

send_message ~1,513

Sends one WhatsApp message into one conversation that already exists, named by conversation_id. It reaches a real person on their phone, and a sent message is final. Each send needs a confirmed call: without confirmation_token the call is a preview that returns what would happen and a token for a person to approve; called again with that token, it sends. Changing a single character between the two calls invalidates the token. A chat nobody holds, or one this person holds, is sent to as usual, and sending does not lock it. A chat another person holds in the Cosend Inbox stays theirs: the preview and the send both return conversation_locked, naming who holds it. To send there, ask them for the chat; it passes over when they say yes or do not answer within 60 seconds. A chat changes hands only when its holder is asked. Each call sends into the one existing conversation its conversation_id names; recipient lists, tags and phone numbers are outside its arguments. Messaging many customers, including contacts with no chat on this number, goes out as a campaign: an approved marketing template sent to a saved audience, once a person approves its preview. Limits per workspace: 20 a minute, 200 a day, and one per conversation every 30 seconds. The 24-hour customer service window opens when the customer writes and starts again with each message from them; outside it, anything but an approved template is refused. A send needs no opt-in. Only an opt-out on this number stops it: a STOP, WhatsApp’s own opt-out or an owner’s entry. A STOP to one number stops sends on that number only, and the business’s other numbers keep sending.

NameTypeReqDescription
audioobject–Meta's media object. `id` may be a Cosend media id (`med_…`, from `POST /v1/media`): Cosend uploads the file to WhatsApp and sends it by WhatsApp's id, and the message's `media` block then names the…
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
contactsarray––
conversation_idstringyes–
documentobject–Meta's media object. `id` may be a Cosend media id (`med_…`, from `POST /v1/media`): Cosend uploads the file to WhatsApp and sends it by WhatsApp's id, and the message's `media` block then names the…
fallback_templateobject––
imageobject–Meta's media object. `id` may be a Cosend media id (`med_…`, from `POST /v1/media`): Cosend uploads the file to WhatsApp and sends it by WhatsApp's id, and the message's `media` block then names the…
interactive––Meta's interactive object. Checked against WhatsApp's limits before anything is written, and refused in words naming the field: a reply-button message (type "button", up to 3 buttons), a list message…
locationobject––
metadataobject––
reactionobject––
reply_to–––
send_modestring––
sourcestring–Who is sending. Left out, it is agent for a person (the dashboard Inbox, or an MCP client acting for one) and api for an API key.
stickerobject–Meta's media object. `id` may be a Cosend media id (`med_…`, from `POST /v1/media`): Cosend uploads the file to WhatsApp and sends it by WhatsApp's id, and the message's `media` block then names the…
templateobject–Meta's template object: {"name", "language": {"code"}, "components"}. A header parameter of type image, video or document may name a file uploaded with POST /v1/media by its id ({"type": "image", "im…
textobject––
typestringyes–
videoobject–Meta's media object. `id` may be a Cosend media id (`med_…`, from `POST /v1/media`): Cosend uploads the file to WhatsApp and sends it by WhatsApp's id, and the message's `media` block then names the…

No output schema declared.

No examples provided.

set_contact_consent ~130

Records a contact's marketing or utility consent as a new entry in an append-only ledger. Every entry is kept as written, so this is an audit record of what the business was told. A send needs no recorded opt-in. An opt-out recorded here stops that category on the number it is recorded for, and the business’s other numbers keep sending.

NameTypeReqDescription
categorystringyes–
connection_idstring––
evidenceobject––
idstringyesThe id in the resource path.
sourcestring––
statestringyes–

No output schema declared.

No examples provided.

set_up_accurate_warehouse_arrival ~381

Sets up Cosend’s “Warehouse arrival message” automation on one WhatsApp number: When an Accurate shipment reaches the warehouse, its receiver gets one WhatsApp message with the shipment’s details. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. It needs accurate, and http connected to the workspace first (by integration key). Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_ai_receptionist ~361

Sets up Cosend’s “AI receptionist” automation on one WhatsApp number: Answers your customers on WhatsApp from what you teach it, and passes a chat to you when needed. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_appointment_reminder ~388

Sets up Cosend’s “Appointment reminder” automation on one WhatsApp number: Customers get a reminder before each booking, and you choose what Confirm, Reschedule and a typed reply do. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. It needs google_calendar or microsoft_calendar or calendly or cal_com or bokun connected to the workspace first (by integration key). Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_lead_capture ~362

Sets up Cosend’s “Lead capture from ads” automation on one WhatsApp number: People who message you from an ad answer your questions one at a time, and you get their answers. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_missed_call_text_back ~366

Sets up Cosend’s “Missed call text-back” automation on one WhatsApp number: When a customer calls your WhatsApp number and nobody picks up, they get a message from you straight away. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_order_confirmation ~373

Sets up Cosend’s “Order confirmation” automation on one WhatsApp number: When a customer pays in your shop, they get a WhatsApp message with the order number and total. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. It needs woocommerce connected to the workspace first (by integration key). Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_order_updates ~375

Sets up Cosend’s “Shipping and cancellation updates” automation on one WhatsApp number: Customers get a WhatsApp message with their tracking when an order ships, and another if it is cancelled. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. It needs woocommerce connected to the workspace first (by integration key). Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_payment_reminder ~377

Sets up Cosend’s “Payment reminder” automation on one WhatsApp number: Customers get WhatsApp reminders before and after an invoice in your Google Sheet is due, until you mark it paid. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. It needs google_sheets connected to the workspace first (by integration key). Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_quote_intake ~359

Sets up Cosend’s “Quote requests” automation on one WhatsApp number: Customers who ask for a quote answer your questions, then the chat comes to you with their answers. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_review_request ~360

Sets up Cosend’s “Review request” automation on one WhatsApp number: Tag a customer when the job is done, and a few hours later they get your request for a review. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

set_up_welcome_menu ~364

Sets up Cosend’s “Welcome and away menu” automation on one WhatsApp number: Greets new customers, and anyone who writes while you are closed, with buttons for quick answers or a person. Its settings are this recipe’s own, as its set-up form in Cosend asks them; a setting left out takes its default. It is set up switched off, and acts only once it is switched on. The same recipe is set up once on each number, or once per source when it asks for one. The preview refuses a second one as the save would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the automation, switched off.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyesThe WhatsApp number (connection id) this automation belongs to: its triggers come from it, its messages go from it, and its templates are read on it. Required, and it cannot be moved afterwards. The…
namestring–Its name in Cosend. Left out, it takes the recipe’s name.
settingsobjectyesThe recipe’s settings, as its set-up form asks them. A setting left out takes its default; a setting with no default is needed.

No output schema declared.

No examples provided.

stop_cosend_number ~219

Stops a phone number from Cosend, named by id (cnm_…), that is verifying or ready, and returns it stopping, with release_at, its last day: an hour before the billing period ends. On that day any WhatsApp connection on it is disconnected and the number is given back for good; nothing is refunded, and nothing more is billed for it. It acts only on a confirmed call: without confirmation_token it changes nothing and returns a preview of the number and a token for a person to approve; the number’s status, last day and WhatsApp connection are read again when the token comes back. Only a person’s approval stops it. Owners and admins; a workspace with an unpaid invoice may stop one too.

NameTypeReqDescription
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
idstringyesThe Cosend number (cnm_…) to stop.

No output schema declared.

No examples provided.

submit_template ~859

Creates a new WhatsApp message template and sends it to Meta for review. This leaves Cosend: Meta reviews every template (a decision can take up to 24 hours), and a rejection counts against the WhatsApp account’s quality history. Each submission needs a confirmed call: without confirmation_token the call is a preview that returns what would happen and a token for a person to approve; called again with that token, it submits. Ten a day per workspace. The categories: marketing makes people aware of the business, its offers and sales; utility follows up on something the customer did or asked for (an order, a booking) and may not promote anything, so an order update with a discount in it is marketing; authentication is a one-time code. A wrong category is moved or rejected by Meta. Meta’s answer shows in the template’s review status. It sends no message to anyone.

NameTypeReqDescription
authentication––An authentication template, in Meta's shape, in place of components and language: {"languages": ["fr", "en_US"], "add_security_recommendation": true, "code_expiration_minutes": 10, "delivery": {"type…
categorystringyes–
componentsarray–Meta's components; required on every category but authentication, which takes authentication instead. A HEADER carries its format (TEXT, IMAGE, VIDEO, DOCUMENT or LOCATION), and a header without one…
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
connection_idstringyes–
display_namestring–The human name, free text (e.g. "Order shipped"). When name is left out, the system name is generated from it: lowercase, accents dropped, every other run of characters an underscore, at most 512 cha…
example_valuesobject–A sample value for every variable in the TEXT header and the body, keyed per component by the name between the braces: {"body": {"1": "Pablo", "2": "860198-230332"}} or {"body": {"first_name": "Pablo…
languagestring–The language, e.g. "en_US". Required on every category but authentication, which takes authentication.languages instead.
namestring–The system name, used as given. Optional: leave it out and it is generated from display_name. Give it to add a language to an existing template. One of name and display_name is required.
parameter_formatstring––

No output schema declared.

No examples provided.

switch_off_automation ~77

Switches one automation off at once, so it starts on nothing from then on. It needs no confirmation, so it works as an emergency stop. Messages it already sent stay sent. A recipe set up with a second automation switches off with it. Returns the automation.

NameTypeReqDescription
idstringyesThe id in the resource path.

No output schema declared.

No examples provided.

switch_on_automation ~358

Switches one automation on, running the version named (version_id), older or newer, got ready first if it never was; left out, the newest, which deploy_automation gets ready first. A version with a step that has to be confirmed by name is got ready with deploy_automation and confirm_actions first. From then on it acts on its own whenever what it starts on happens, and its steps run as they are built, which can include WhatsApp messages to customers. A recipe set up with a second automation switches on with it. actions names every action the version’s steps take, and the second automation’s, from the list in the schema (an automation’s versions list theirs as actions); a list that leaves one out or names another is refused, with the right list. The preview refuses that list as the call would, and gives no token. Each call needs confirming: without confirmation_token it changes nothing and returns a preview and a token for a person to approve; called again with that token, it switches it on.

NameTypeReqDescription
actionsarrayyesEvery action the automation’s steps take, and those of a second automation set up with it, each once: what a person approves it doing. A list that leaves one out, or names one the steps do not take,…
confirmation_tokenstring–For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it.
idstringyesThe id in the resource path.
version_idstring––

No output schema declared.

No examples provided.

sync_templates ~69

Reads the templates of one WhatsApp number from Meta now, updates what Cosend holds to match, and returns the synced list. connection_id is the number. Templates Meta changed since the last sync, such as a decision or a new category, show up here.

NameTypeReqDescription
connection_idstringyes–

No output schema declared.

No examples provided.

tag_contact ~114

Adds tags to, or removes tags from, one contact, named by id, without touching the rest of its tags. action add leaves a tag the contact already has as it is; action remove skips a tag it does not have. tags is the list of tag names. The change stays inside Cosend. Returns the contact.

NameTypeReqDescription
actionstringyesadd to put tags on the contact, remove to take them off.
idstringyesThe id in the resource path.
tagsarrayyes–

No output schema declared.

No examples provided.

take_over_conversation ~146

Puts one conversation, named by id, in a person’s hands: control human means a person holds it and the AI assistant and automations stop answering in it; control pending_human marks it as waiting for a person to pick up. reason says why, and pause_bot_until holds the assistant back until a time. It hands the chat to a person; the chat stays with people from then on. The change stays inside Cosend, out of the customer’s view. Returns the conversation.

NameTypeReqDescription
controlstringyes–
idstringyesThe id in the resource path.
pause_bot_untilstring––
reasonstring––

No output schema declared.

No examples provided.

template_check ~426

Checks a WhatsApp message template (category, language, components and example values, as Meta takes them) against Meta’s rules, which are errors, and the warning signals Meta names, which are warnings; each problem says where it is and what to change. The verdict is fix_first, warnings or ready, and ready is not an approval: Meta still reviews every template itself. Nothing is submitted.

NameTypeReqDescription
authentication––An authentication template, in Meta's shape, in place of components and language: {"languages": ["fr", "en_US"], "add_security_recommendation": true, "code_expiration_minutes": 10, "delivery": {"type…
categorystringyes–
componentsarray–Meta's components, as POST /v1/templates takes them; required on every category but authentication, which takes authentication instead.
example_valuesobject–A sample value for every variable in the TEXT header and the body, keyed per component by the name between the braces: {"body": {"1": "Pablo", "2": "860198-230332"}} or {"body": {"first_name": "Pablo…
languagestring–The language, e.g. "en_US". Required on every category but authentication, which takes authentication.languages instead.
parameter_formatstring––

No output schema declared.

No examples provided.

Install

How do I install the Cosend MCP server?

Cosend is a hosted endpoint at https://mcp.cosend.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.cosend.app

# add to Claude Code
claude mcp add --transport http app-cosend-mcp 'https://mcp.cosend.app/mcp'
Common questions

What is the Cosend MCP server?

Cosend is an MCP server listed in the public MCP registry as app.cosend/mcp. WhatsApp Business inbox for AI apps: read and answer chats, run campaigns, deploy automations. This page covers its hosted endpoint (https://mcp.cosend.app/mcp).

Is the Cosend MCP server safe to use?

Cosend scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Cosend MCP server expose?

Cosend exposes 125 tools: whoami, list_conversations, search_conversations, read_conversation, send_message, and 120 more. Their descriptions and schemas cost roughly 29,877 tokens of context every time the server is loaded.

Does the Cosend MCP server require authentication?

Yes. Cosend asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Cosend MCP server still maintained?

Cosend is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Cosend MCP server?

VerifyMCP ran 13 checks on Cosend, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.