Skip to content
Whats91

Connect an AI assistant to Whats91 through the Model Context Protocol and give it safe, scoped access to your WhatsApp workspace.

Whats91 MCP

Summary

Connect an AI assistant to Whats91 through the Model Context Protocol and give it safe, scoped access to your WhatsApp workspace.

Prerequisites

  • A Whats91 account
  • A generated public API token

The Whats91 MCP server lets an AI assistant work inside your Whats91 workspace: read reports, draft templates, prepare campaigns, manage contacts, and send messages. It is a separate product from the REST API. Where the REST API is designed for your own backend, MCP is designed for an autonomous or semi-autonomous client that needs guard rails.

https://graph.whats91.com/mcp

Endpoint

A single stateless JSON-RPC 2.0 endpoint. POST only.

151

Tools

Registered tools across 14 groups, each with a declared scope and safety class.

OAuth 2.1

Authorization

Authorization code with PKCE, dynamic client registration, and per-scope consent.

6

Safety classes

Every tool declares one, which determines approval, preview, retry, and audit behaviour.

MCP Compared With the REST API

REST APIMCP
AudienceYour backend, written by youAn AI client acting on a user behalf
Basehttps://graph.whats91.com/api/{version}https://graph.whats91.com/mcp
VersioningPath version: v2, v3Per-tool version plus a negotiated protocol version
AuthPublic API bearer tokenOAuth 2.1 access token with granular scopes
ShapeREST resources, HTTP verbsJSON-RPC 2.0 tool calls
Guard railsYour code decides what is safeDeclared safety classes, prepare/confirm, approvals, audit

Tip

Use the REST API when your own code is in control of the decision. Use MCP when a model is in control and you need the platform to enforce what it may do.

What an MCP Client Can Do

GroupToolsTypical use
Diagnostics4Connectivity, identity, negotiated capabilities, and the tools-only operational guide.
Messaging3Send approved templates and session chat messages, and inspect a message operation.
Templates13Read, validate, draft, duplicate, submit, and delete WhatsApp templates.
Campaigns21Build, validate, test-send, execute, pause, resume, and cancel campaigns and recurrences.
Contacts18Read and write contacts, contact books, memberships, and bulk imports.
Chatbots and Flows26Manage chatbots, and draft, validate, simulate, version, and publish chatbot flows.
WhatsApp Forms17Create, validate, preview, publish, deprecate, and archive forms, and read submissions.
Catalogs14Read catalogs and products, write product records, and drive catalog synchronisation.
Orders9Read orders, check payment readiness, transition order status, and retry order automation.
Media11List and read media, check usage and limits, upload new media, and delete media.
Conversations5Find conversations, read history, and check the 24-hour customer service window.
Blacklist8Check, list, add, bulk-add, and remove blocked recipients.
Reports1Summarised message reporting for an agent conversation.
Billing1Read wallet balance, plan status, and message category rates.

Getting Started

  1. Register an OAuth client, or use a pre-provisioned client id.
  2. Complete the authorization code flow with PKCE and request only the scopes your client needs.
  3. Send initialize to negotiate the protocol version and read server capabilities.
  4. Call tools/list to discover the tools your granted scopes actually expose.
  5. Call whats91_whoami and whats91_connection_info to confirm tenant identity and operational readiness.
  6. Start with read-only tools, then adopt writes through the prepare and confirm pattern.

Related Documentation