Wagate

dev.wagatev0.2.0Updated Oct 26, 2026

Read WhatsApp chats and groups, and send messages when allowed, through the WaGate API.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that lets an assistant read WhatsApp chats and groups and, when explicitly enabled, send messages via the WaGate API.

What you can do
  • Read WhatsApp chats and group conversations through the WaGate API.
  • Send messages from the configured channel, but only when the send tools are explicitly enabled.
  • Work against a specific channel identified by its channel ID and API token.
  • Point at a custom API base URL instead of the default WaGate endpoint.
When to use it
Useful when you want an assistant to look through WhatsApp chats and groups, or to draft and send replies from a WaGate-connected channel. Sending stays off unless you deliberately turn it on.
Requirements
Runs locally over stdio via npx from the npm package @wagate/mcp, so Node.js is needed. Requires a WaGate channel ID (GATEWAY_CHANNEL_ID) and the channel's API token (GATEWAY_API_TOKEN). GATEWAY_API_URL is optional and defaults to the WaGate API endpoint. Network access to the WaGate API is required.
Before you install
The API token is a secret that grants access to the channel's WhatsApp data; keep it out of shared configs. Send tools are off by default and are enabled with GATEWAY_ALLOW_SEND, so turning them on lets the assistant post real messages to chats and groups. Chat content is sent to the WaGate API, a third party.

Installation

In SourceWeft

  1. Open Wagate in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package did not install.

Version history

1
  1. v0.2.0LatestOct 21, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.