WATI MCP Server

The WATI MCP Server lets compatible AI clients securely work with WATI and, for linked accounts, Astra capabilities through one remote MCP connection. It is designed for operational workflows such as finding contacts and conversations, sending approved messages, managing templates and webhooks, and working with campaigns and segments.

This is the product MCP service. It is distinct from https://docs.wati.io/mcp, which serves the ReadMe API-reference MCP.

Connect

Use the remote Streamable HTTP endpoint:

https://mcp.wati.io/mcp

In an MCP client that supports a remote URL configuration, add the endpoint and reconnect. For example:

{
  "mcpServers": {
    "wati": {
      "url": "https://mcp.wati.io/mcp"
    }
  }
}

Your client should then open the OAuth sign-in flow. The server publishes standard OAuth discovery metadata at:

• https://mcp.wati.io/.well-known/oauth-authorization-server
• https://mcp.wati.io/.well-known/oauth-protected-resource

Do not put bearer tokens, API keys, or other credentials in query parameters. Use your MCP client's OAuth flow and its supported secure credential storage.

What is available

The exact result of tools/list is authoritative for the signed-in user. Depending on the connected account, the server can expose WATI capabilities including:

• Contacts and contact attributes
• Conversations, conversation tags, status, assignment, and messages
• Templates, campaigns, credits, and send-cost estimates
• Segments, channels, and webhooks
• Instagram workflows where enabled
• Workspace discovery and active-workspace management

A linked Astra account can additionally expose Astra capabilities such as agent, knowledge, testing, skills, and integration workflows.

Availability and permissions

Tools are intentionally not visible to every connection. Availability depends on the OAuth capabilities granted to the connection, the user's WATI account binding, tenant-level rollout or entitlement, and—in the case of Instagram—an additional feature gate. If a tool is not returned by tools/list, do not assume it is supported for that account.

Choose the correct workspace

WATI operations act on the active workspace. Before a write operation, first confirm the destination with wati_get_active_tenant. If you have access to multiple workspaces, use wati_list_tenants and then wati_switch_tenant.

The first switch to a workspace can require a browser sign-in; later switches reuse the verified session. Always confirm the active workspace again before sending a message, changing a contact, or modifying a webhook.

Safe first use

1. Connect to https://mcp.wati.io/mcp and complete OAuth.
2. Inspect tools/list in your MCP client.
3. Check the active workspace with wati_get_active_tenant.
4. Start with a read operation, such as listing contacts, templates, campaigns, or channels.
5. Before a write operation, state the intended workspace and action clearly, then use the relevant tool.

Troubleshooting

• 401 or an authentication prompt: complete OAuth again and reconnect the client.
• No WATI tools are listed: the account may be missing a WATI binding, the required capability, or rollout entitlement.
• A different workspace is needed: list accessible workspaces and switch explicitly; do not pass a tenant identifier to unrelated tools.
• A workspace session has expired: use wati_switch_tenant to sign in to that workspace again.

For the WATI REST API itself, use the API Reference sections in this documentation site.