WhatSync
app.whatsyncPublished by whatsync.appOfficial publisherv1.0.0Updated Oct 24, 2026
WhatsApp for Claude, ChatGPT or any AI agent: search, reply and send. Personal or Business API.
Overview
Lets an AI assistant search, read, reply to, and send WhatsApp messages through a hosted remote endpoint.
- What you can do
- WhatSync connects an AI assistant to WhatsApp so it can search conversations, read messages, reply to existing threads, and send new messages. It is offered as a remote MCP endpoint with support for personal or business WhatsApp accounts. The manifest lists no individual tools, so the exact tool set is not documented here.
- When to use it
- Worth considering when you want an assistant to handle WhatsApp conversations directly, for example drafting replies, finding past messages, or sending notifications from a chat-based workflow. It is less useful if you only need read-only access or do not want a third-party service in the message path.
- Requirements
- A remote MCP client that supports streamable HTTP, plus OAuth sign-in to the WhatSync service. No environment variables or headers are declared. A WhatsApp account (personal or business) is implied by the description.
Installation
In SourceWeft
- Open WhatSync 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/app.whatsync%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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"whatsync": {
"type": "http",
"url": "https://whatsync.app/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 14, 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.