LetsBot
by LetsBot
Read and send WhatsApp Business messages from an AI agent. Anthropic lists 58 tools including 11 send_ tools and a bulk campaign builder. OAuth 2.1 or a bearer API key, and no OAuth scopes are advertised anywhere.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect LetsBot via MCP
https://letsbot.net/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
LetsBot Tools & Capabilities (58)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Fifteen tools send to a real phone and none of them is reversible. No tool in either enumeration recalls, edits or deletes a sent WhatsApp message. Auto-approving any
send_tool,reply_to_message,forward_messageorcreate_campaignis a decision about irreversible outbound contact, and we counter-recommend blanket approval for all fifteen. create_campaignreaches a list, not a person. One call targets every contact carrying a label. LetsBot's documented ceiling is your Meta tier — up to 100,000 recipients a day at Tier 4. There is no dry-run, preview or recipient-count tool in the listing that returns the campaign size before the send;get_label_contactscan be called first, but nothing requires it.- No OAuth scopes exist at all. Neither the resource descriptor nor the authorization server advertises
scopes_supported. Nothing at the OAuth grant separates reading a conversation from sending a campaign. The read-only option LetsBot documents exists only on the bearer-key path. - The two tool enumerations disagree, and the disagreement includes an outbound tool.
send_carouselis documented by LetsBot and absent from the directory listing, and it targets Messenger and Instagram rather than WhatsApp. Whether the live server exposes it is unverified. - Three tool names appear only in the vendor's worked examples.
get_conversations,get_abandoned_cartsandsend_bulk_campaignare named in prompt illustrations and exist in no enumeration. Do not write a workflow against them. - Bot-configuration tools defer outbound capability past the confirmation prompt.
create_simple_conversation,create_interactive_conversation,update_bot_conversationandupdate_bot_settingswrite auto-reply rules that message customers afterwards, unattended. - WhatsApp policy is documented elsewhere and not enforced here. Meta template approval, opt-out handling and quality-rating tiers appear on LetsBot's bulk-messaging page, not on the MCP page and not in any tool description. No opt-in requirement is stated anywhere in LetsBot's documentation we read. LetsBot's own material warns that policy violations risk "a permanent Meta-level number ban".
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here, and the read/write split is our classification rather than the server's declaration.
- Rate limiting is visible but undocumented. The endpoint returned
x-ratelimit-limit: 30on an anonymous request; LetsBot's FAQ states there is no separate MCP cap and that usage counts against the plan's message allowance. Per-plan message costs are not published on the MCP page, so the monetary cost of a campaign launched by an agent is not predictable from the documentation. - Where the connector's own copy overstates. LetsBot's MCP page claims "OAuth 2.1 fully RFC-compliant" while the same page's setup steps and error body direct you to a bearer API key, and its ChatGPT card names three scopes that appear in no metadata document.
Frequently asked questions
Yes. Eleven tools carry a send verb, and four more deliver message content: reply_to_message, send_reaction, forward_message and create_campaign. A sent WhatsApp message lands on someone's personal phone, cannot be unsent through this surface, and no tool in the listing deletes or recalls one. Treat every send tool as irreversible.
Yes, through create_campaign. LetsBot describes it as a label-targeted bulk message campaign, so one call reaches every contact carrying a label rather than one recipient. LetsBot's bulk-messaging page states official campaigns send at 3-4 seconds per message with unlimited daily volume, subject to your Meta tier. That is the highest-consequence call on this connector.
None are advertised. The RFC 9728 resource descriptor at letsbot.net returned no scopes_supported field on 2026-08-23, and neither did the authorization server metadata. So the consent screen offers no way to grant reading a conversation without also granting sending a message or launching a campaign to your whole contact list.
Yes, both. get_messages and search_messages return conversation text, and get_contacts and get_contact return contact records. That is third-party personal data belonging to people who messaged your business, not to you. Those people consented to talk to your company, not to have their messages read by an AI vendor.
LetsBot documents the rules but never applies them to the MCP surface. Its bulk-messaging page states marketing messages need Meta-approved templates reviewed in about 24 hours, and describes an opt-out list. Neither the MCP page nor the tool descriptions repeat that, so an agent calling send_text_message gets no template gate from the documentation.
Yes, with a bearer key rather than OAuth. LetsBot states you pick read-only or full-access scope when generating an API key in the dashboard, and recommends read-only for reporting workflows. That boundary exists only on the API-key path. The OAuth flow Claude uses advertises no scopes at all, so it offers no equivalent choice.
The two sources disagree. Anthropic's directory lists 58 names, LetsBot's MCP page enumerates 57, and LetsBot's own Claude page says 58. The lists are not the same 57 either: the directory carries two AI reporting tools the MCP page omits, and the MCP page carries one send tool the directory omits.
No tool in either list carries a delete or remove verb. The nearest destructive names are block_contact and archive_contact, which LetsBot documents as toggles, so both reverse. That absence cuts the other way too: nothing here can undo a send, so the irreversible action on this connector is delivery, not deletion.
Sources
- LetsBot WhatsApp MCP documentation (retrieved 2026-08-23). The nominated documentation URL, and the winner of a four-route probe:
llms.txt,llms-full.txtand both.mdsuffix routes all returned 404. · retrieved 2026-08-23 - LetsBot Claude connector page (retrieved 2026-08-23). Not in the sitemap; found by following links from the MCP page. Source of the "58 tools" count that contradicts the MCP page. · retrieved 2026-08-23
- LetsBot bulk messaging (retrieved 2026-08-23). Source of the Meta template-approval, tier and opt-out statements. · retrieved 2026-08-23
- LetsBot FAQ (retrieved 2026-08-23) · retrieved 2026-08-23
- LetsBot WhatsApp Business API page (retrieved 2026-08-23) · retrieved 2026-08-23
- LetsBot for developers (retrieved 2026-08-23). Links to
docs.letsbot.net, which redirects to a Postman collection viewer that renders client-side and yielded no readable content. · retrieved 2026-08-23 - LetsBot privacy policy (retrieved 2026-08-23) · retrieved 2026-08-23
- Live auth posture check: anonymous initialize to
https://letsbot.net/mcpreturned HTTP 401 with awww-authenticateBearer challenge naming its resource metadata document (2026-08-23) · retrieved 2026-08-23 - RFC 9728 resource metadata —
https://letsbot.net/.well-known/oauth-protected-resource/mcp, and authorization server metadata athttps://letsbot.net/.well-known/oauth-authorization-server, both 200 with noscopes_supported(2026-08-23) · retrieved 2026-08-23 - LetsBot
robots.txt(retrieved 2026-08-23). Allows all crawlable paths used here; noContent-Signaldirective present. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- LetsBot support — <mailto:ceo@letsbot.net> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- LetsBot
- Tools
- 58
- Domain
- letsbot.net
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.