For developers & AI agents
Connect wha.tools to your AI assistant
WhaTools ships a free Model Context Protocol (MCP) server, so an AI assistant can build WhatsApp click-to-chat links, QR codes and share widgets, validate phone numbers, estimate WhatsApp Business API cost, and read the current rate card and limits table: the same tools this site offers, running locally on the server. Read-only, no key, nothing is sent.
https://wha.tools/api/mcpSet it up in your client
Add the server once, then your assistant can call its tools. Every recipe uses the same endpoint above.
Claude Code
Run this once in your terminal: the CLI stores the server for you.
claude mcp add --transport http wha-tools https://wha.tools/api/mcpClaude Desktop
Add to Settings → Developer → Edit Config (claude_desktop_config.json). The mcp-remote bridge lets a desktop client reach a remote HTTP server.
{
"mcpServers": {
"wha-tools": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://wha.tools/api/mcp"]
}
}
}Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).
{
"mcpServers": {
"wha-tools": {
"url": "https://wha.tools/api/mcp"
}
}
}VS Code (GitHub Copilot)
Add to .vscode/mcp.json in your workspace.
{
"servers": {
"wha-tools": {
"type": "http",
"url": "https://wha.tools/api/mcp"
}
}
}Any other MCP client
Point it at the endpoint as a Streamable HTTP (remote) server. No authentication header is required.
https://wha.tools/api/mcpWhat your assistant can do
8 tools, all local and read-only. This list is generated from the server itself, so it always matches what the endpoint advertises.
generate_whatsapp_link- Generate a WhatsApp click-to-chat (wa.me) link with an optional phone number and pre-filled message. Runs locally; no message is sent.
generate_bulk_whatsapp_links- Generate personalized WhatsApp click-to-chat (wa.me) links for a list of contacts from one message template. Everything uses a single {{…}} syntax: {{field}} placeholders are replaced per contact; {{field|fallback}} supplies a default for empty/missing fields; {{FirstName}} is derived from a name field; and {{option a|option b}} spintax (a group whose first option is not a field) picks one variation per contact (stable per number) so messages are not identical. Returns a JSON array of {phone, message, link}. Runs locally; no message is sent: each link opens WhatsApp with the text pre-filled and a human taps send.
validate_phone_number- Validate and inspect a phone number with libphonenumber: whether it is valid (a real, allocated number) and/or possible (right length), its country, calling code, line type (mobile / landline / VoIP / toll-free / …) and every standard format (E.164, international, national) plus a wa.me link. Runs locally and offline. Does NOT check whether the number is registered on WhatsApp. There is no such API here.
generate_whatsapp_qr- Generate a scannable QR code (as an SVG) for a WhatsApp click-to-chat link with an optional phone number and pre-filled message.
build_whatsapp_share_widget- Build embeddable "Share on WhatsApp" widget HTML (web and email variants) with a link preview card and a pre-filled message. Returns self-contained HTML.
estimate_whatsapp_api_cost- Estimate the monthly WhatsApp Business (Cloud) API cost under Meta's per-message pricing (in effect since 1 July 2025). Given a country/market and monthly volumes of marketing, utility, authentication and (optionally) service messages, returns an itemized breakdown and total in USD. Marketing is always billed; utility and authentication are billed with volume-tier discounts in many markets. As of 1 October 2026 utility is billed even inside the customer-service window (previously free there), and service messages are billed at the utility rate with the first 1,000 per phone number each month free. Pass `service` to include them; omit it to leave service out. Runs locally. This is Meta's platform fee only: a BSP/provider adds its own fee on top, so treat it as a floor, not a quote.
get_whatsapp_rates- Look up Meta's official WhatsApp Business (Cloud) API per-message rates from the site's dated rate card, the same figures the pricing calculator uses, so prefer this over recalling or guessing prices. Give a market to get one row, or omit it for every market in the chosen currency. Returns the current list price per template category (marketing, utility, authentication, and authentication-international where a market has one), the currency, the effective and last-verified dates, the source link and the CC BY licence. Optionally include the published volume-tier thresholds and rates for a single market. This is Meta's platform fee only: a BSP/provider adds its own fee on top, so treat it as a floor. Runs locally.
get_whatsapp_limits- Look up WhatsApp's current limits and rules from the site's dated reference table: group and community size, broadcast lists, message and media/file sizes, character counts, forwarding, calls, Channels, linked devices, and WhatsApp Business app and Business API limits. Each value is single-sourced and dated. Returns the limits (optionally filtered to one area), the last-verified date, the source and the CC BY licence. Prefer this over recalling limits from memory. They change over time. Runs locally.
Machine-readable discovery
For directories, registries and agents that find servers on their own.
- MCP Server Card
/.well-known/mcp/server-card.jsonThe endpoint, protocol version and tool list (draft SEP-1649): how a client auto-discovers this server.
- OpenAPI 3.1
/openapi.jsonDescription of the public HTTP API (health, open data, link preview, and the MCP pointer).
- API catalog
/.well-known/api-catalogRFC 9727 linkset indexing every machine-readable resource on the site.
- llms.txt
/llms.txtCurated Markdown index of the site for LLMs and agents.
- Open data (JSON)
/api/dataThe rate card, limits table and pricing change ledger under CC BY 4.0: the same data the two data tools return.
- Health
/api/healthLiveness and running version.
Frequently Asked Questions
wa.me link, a QR image, widget HTML or JSON. Nothing is ever sent to WhatsApp; a human still taps send.mcp-remote), Cursor and VS Code are shown above, and other MCP clients work the same way by pointing at the endpoint.