io.2chatPublished by 2chat.ioOfficial publisherv1.0.0Updated Oct 24, 2026

WhatsApp (Web + Business API), SMS, contacts, and call records via 2Chat's MCP server.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Server details

Identifier: io.2chat/whatsapp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to 2chat.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.2chat%2Fwhatsapp.svg)](https://sourceweft.com/mcp/io.2chat%2Fwhatsapp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant work with WhatsApp, SMS, contacts and call records through 2Chat's hosted MCP endpoint.

What you can do: This is a remote MCP server operated by 2Chat that exposes WhatsApp (Web and Business API), SMS, contacts and call records to an assistant. The registry description lists those four areas as its scope, so an assistant can reach messaging and contact data through one endpoint rather than separate integrations. No individual tools are documented in the supplied material, so the exact operations are not specified here.
When to use it: Consider it when an assistant needs to read or act on WhatsApp and SMS messaging, contact lists, or call records that already live in a 2Chat account. It suits hosted setups where you prefer a remote endpoint over running a local process.
Requirements: A remote streamable HTTP endpoint at the provider's host; no local package or runtime is declared. OAuth authentication is required, so you need a 2Chat account and must complete the OAuth flow. No environment variables or headers are declared.

Before you install

The server is hosted by a third party, so messaging content, contact details and call records handled through it pass to that provider. OAuth grants the assistant access to your 2Chat account; review the scopes before authorizing. Because it covers messaging, an assistant may be able to send messages or change contact data, so confirm what it can write before enabling it.

Installation

In SourceWeft

Open Whatsapp in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.2chat%2Fwhatsapp/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": {
    "whatsapp": {
      "type": "http",
      "url": "https://mcp.2chat.io/mcp"
    }
  }
}

Tools

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

v1.0.0LatestSep 16, 2026

Score

56% 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
Publish an icon in the registry entry.
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.

Whatsapp