WSENDER

io.wsenderPublished by wsender.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Manage WhatsApp, Telegram and MAX mailings: audiences, drafts, moderation and sending.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant manage WhatsApp, Telegram and MAX mailings, including audiences, drafts, moderation and sending.

What you can do
Manage audiences for WhatsApp, Telegram and MAX mailings, including audience setup and upkeep as described in the registry entry. Create and edit mailing drafts before they go out. Moderate mailings, reviewing content before it is sent. Send mailings through the connected messaging channels. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Useful when you run outreach or broadcast campaigns on WhatsApp, Telegram or MAX and want an assistant to help prepare audiences, draft and review messages, and trigger sends without switching between tools.
Requirements
A remote MCP server reached over streamable HTTP at its hosted endpoint; no local package or runtime is needed. Authentication is OAuth and is required, so you need an account with the provider and must complete the OAuth sign-in flow. A web-executable client is supported.
Before you install
The server can send mailings to real recipients, so actions may be public and hard to undo. It handles audience data, which may include personal contact details sent to the provider. Review drafts and moderation steps before allowing any send, and confirm which account and channels the OAuth grant authorizes.

Installation

In SourceWeft

  1. Open WSENDER 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/io.wsender%2Fwsender/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": {
    "wsender": {
      "type": "http",
      "url": "https://mcp.wsender.io/"
    }
  }
}

README

This repository has no README.

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.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.