Leporis WhatsApp

io.github.admin-rstechiePublished by GitHub account admin-rstechiev1.0.0Updated Oct 25, 2026

Send and read WhatsApp messages on your Leporis account from AI coding agents, via your own API key.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an AI assistant send and read WhatsApp messages, contacts and conversations on a Leporis account using your own API key.

What you can do
Send WhatsApp messages from chat through the Leporis account's public API tools (send_message). List and look up contacts (list_contacts, get_contact). Retrieve the messages of a conversation (get_conversation_messages).
When to use it
Useful when you work in an AI coding agent or chat client and want to send or review WhatsApp messages on a Leporis Business account without leaving the conversation.
Requirements
A remote Streamable HTTP endpoint; no local install needed. A Leporis account and API key, generated in the Leporis dashboard under WhatsApp, Integrations, sent as an Authorization Bearer token on every request. Network access to the endpoint.
Before you install
The API key is a secret sent in the Authorization header on every request; keep it out of shared configs. Sending messages writes to a real WhatsApp account and reaches real recipients, so review outgoing content before it is sent. Message and contact data is passed to the remote Leporis service.

Installation

In SourceWeft

  1. Open Leporis WhatsApp in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.github.admin-rstechie%2Fleporis-mcp/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.

{
  "mcpServers": {
    "leporis-whatsapp": {
      "type": "http",
      "url": "https://leporis.mcp.rstechie.in/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

leporis-mcp

Remote MCP (Model Context Protocol) server for Leporis, RS-Techie's multi-tenant WhatsApp Business platform.

Exposes Leporis's public REST API (api/v1/public.php) as MCP tools so AI coding agents (Claude Code, Cursor, Antigravity, etc.) can send/read WhatsApp messages on your Leporis account directly from chat.

  • Endpoint: https://leporis.mcp.rstechie.in/mcp (Streamable HTTP transport)
  • Auth: stateless BYOK (bring your own key) — send your Leporis API key as Authorization: Bearer <key> on every request. Get a key from your Leporis dashboard under WhatsApp → Integrations. The server stores no credentials of its own.
  • Tools: send_message, list_contacts, get_contact, get_conversation_messages

Setup in your MCP client

See the "Connect via MCP" section on the Integrations page in your Leporis dashboard for exact per-client config (Claude Code, Cursor, Antigravity).

Running locally

bash
npm installPORT=8806 node server.js

Requires LEPORIS_API_BASE (defaults to https://rstechie.in/api/v1/public.php) to point at a real Leporis instance.

Source: README.md at commit 4cd0cfc

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.