WASync — WhatsApp Platform API
app.wasyncPublished by wasync.appOfficial publisherv1.0.0Updated Oct 24, 2026
WhatsApp for your app or AI agent over OAuth2 — the same connections WASync runs inside your CRM.
Overview
A remote MCP endpoint that connects an assistant to WhatsApp through WASync's platform API using OAuth2, for messaging from apps or agents.
- What you can do
- Connect an assistant to WhatsApp through WASync's hosted platform API over OAuth2, using the same connections WASync runs inside a CRM. The manifest lists no individual tools, so the exact operations are not documented here; the description frames it as WhatsApp messaging access for an app or AI agent. It runs as a remote streamable HTTP endpoint rather than a local package.
- When to use it
- Consider it when you want an AI assistant or app to work with WhatsApp messaging and you already use or plan to use WASync's platform, rather than building a direct WhatsApp integration yourself.
- Requirements
- A remote streamable HTTP endpoint at the provider's cloud host; no local runtime or package is needed. The description mentions OAuth2, so an authorized WASync account and OAuth credentials are presumably required, though the manifest declares no authentication, environment variables or headers. Network access to the endpoint is required.
Installation
In SourceWeft
- Open WASync — WhatsApp Platform API in the dashboard and add it to a workspace.
- 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/app.wasync%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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"wasync-whatsapp-platform-api": {
"type": "http",
"url": "https://cloudapi.wasync.app/api/mcp"
}
}
}Tools
0Version history
1- 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 listedRequired15 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.