LetsBot

Read and send WhatsApp Business messages.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the LetsBot connector does

The LetsBot MCP server connects a WhatsApp Business API account to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 58 tools that read conversations and contacts, send every WhatsApp message type, and create bulk campaigns. Sign-in is OAuth 2.1, or a bearer API key where a client cannot do OAuth.

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.

LetsBot tools (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_message or create_campaign is a decision about irreversible outbound contact, and we counter-recommend blanket approval for all fifteen.
  • create_campaign reaches 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_contacts can 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_carousel is 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_carts and send_bulk_campaign are 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_conversation and update_bot_settings write 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: 30 on 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

Can the LetsBot connector send a WhatsApp message to a real person?

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.

Can the LetsBot MCP server message a whole list at once?

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.

What OAuth scopes does the LetsBot MCP server request?

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.

Does the LetsBot connector read my customers' messages and phone numbers?

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.

Does LetsBot enforce WhatsApp template approval and opt-in rules through MCP?

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.

Can I stop an AI client from sending WhatsApp messages through LetsBot?

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.

How many tools does the LetsBot MCP server actually have?

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.

Can the LetsBot connector delete a WhatsApp message or a contact?

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

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put LetsBot to work.

Connect LetsBot once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.