OTP Run for WhatsApp

com.otprunPublished by otprun.comOfficial publisherv1.2.0Updated Oct 24, 2026

Send WhatsApp messages from your own number, read the replies and send login codes.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant send WhatsApp messages from your own number, read the replies, and send login codes.

What you can do
Send WhatsApp messages from your own phone number on your behalf, as directed by the assistant through the connection. Read incoming replies so the assistant can see how recipients respond. Send login or verification codes over WhatsApp. The manifest lists no individual tools, so the exact set of actions is not documented here.
When to use it
Useful when you want an assistant to reach people over WhatsApp from your own number, for example to send notifications, follow up on conversations, or deliver one-time login codes, and to read the responses that come back.
Requirements
A remote endpoint at otprun.com reached over streamable HTTP. Authentication is required and uses OAuth, so you need an account with the provider and must complete its sign-in and consent flow. No environment variables or headers are declared.
Before you install
Messages are sent from your personal WhatsApp number, so recipients see them as coming from you. The assistant can send messages and login codes to third parties and read the replies, which exposes conversation content to the service. Review what it may send before granting access, and treat login codes as sensitive.

Installation

In SourceWeft

  1. Open OTP Run for WhatsApp 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/com.otprun%2Fotprun/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": {
    "otp-run-for-whatsapp": {
      "type": "http",
      "url": "https://otprun.com/mcp"
    }
  }
}

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.2.0LatestOct 13, 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.