WbizTool

com.wbiztoolPublished by wbiztool.comOfficial publisherv0.1.0Updated Oct 26, 2026

Send WhatsApp and Telegram messages, manage reminders and check numbers in your WbizTool workspace.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

WbizTool's remote MCP server lets an assistant send WhatsApp and Telegram messages, manage reminders and check numbers in a WbizTool workspace.

What you can do
  • Send WhatsApp and Telegram messages from the connected WbizTool workspace
  • Create and manage reminders
  • Check phone numbers in the workspace
  • Authenticate with a WbizTool API v2 key passed as a Bearer token
When to use it
Useful when you want an assistant to push WhatsApp or Telegram notifications, schedule reminders, or verify numbers through an existing WbizTool account rather than a custom integration.
Requirements
A remote MCP endpoint at mcp.wbiztool.com over streamable HTTP, with OAuth authentication. Requires a WbizTool account and an API v2 key from Settings, sent in the Authorization header as a Bearer token. No local package or environment variables are needed.
Before you install
The server holds a WbizTool API key that can act on your workspace; the provider recommends a read-only key unless the assistant should send. Messages sent through it reach real WhatsApp and Telegram recipients and may consume account credits or quota. Review before granting send permissions.

Installation

In SourceWeft

  1. Open WbizTool 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.wbiztool%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": {
    "wbiztool": {
      "type": "http",
      "url": "https://mcp.wbiztool.com/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. v0.1.0LatestOct 18, 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.