LetsBot

net.letsbotPublished by letsbot.netOfficial publisherv1.0.0Updated Oct 31, 2026

WhatsApp Business messaging, live chat, chatbots, campaigns and CRM for a LetsBot workspace.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for a LetsBot workspace that lets an assistant work with WhatsApp Business messaging, live chat, chatbots, campaigns and CRM.

What you can do
  • The listing names no individual tools, so capabilities are described at the workspace level.
  • Work with WhatsApp Business messaging and live chat in a LetsBot workspace.
  • Manage chatbots and messaging campaigns.
  • Access CRM records tied to the workspace.
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in.
When to use it
Worth adding when a team runs its WhatsApp Business conversations, chatbots, campaigns and customer records in LetsBot and wants an assistant to work with that workspace directly instead of switching between tools.
Requirements
A remote MCP endpoint at letsbot.net reached over streamable HTTP, plus a LetsBot workspace account and OAuth authorization. No packages, environment variables or headers are declared.
Before you install
The server acts on live customer messaging and CRM data, so assistant actions may send messages, run campaigns or change records in the workspace. Access is granted through OAuth to the whole workspace, so review the scopes and permissions before connecting.

Installation

In SourceWeft

  1. Open LetsBot in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.letsbot%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "letsbot": {
      "type": "http",
      "url": "https://letsbot.net/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.