MCP Server
Connect Claude, ChatGPT or any MCP-compatible AI agent to Riffre - browse documentation and send WhatsApp messages using the same API key as the REST API.
Last updated 14 Aug 2026
What it is
Riffre runs a standalone MCP (Model Context Protocol) server so AI agents - Claude, ChatGPT, or any MCP-compatible client - can work with your Riffre account directly, without you writing integration code by hand.
It exposes four kinds of tools:
- Documentation tools - list, search and read Riffre's developer documentation. Available with no authentication.
- Conversation tools - list customer numbers and read recent conversation history. Read-only and not billed. Require your Riffre API key.
- Template tools - list templates, check approval status, and submit new templates for Meta approval. Require your Riffre API key.
- Messaging tools - send WhatsApp text, template, media and interactive messages. Require your Riffre API key, and every send is billed to your wallet exactly like the REST API.
Endpoint
POST https://riffrechat.com:3004/mcpThe server uses the MCP Streamable HTTP transport. Configure your MCP client with this URL. Requests are received by the load balancer on port 3004 and forwarded internally to the MCP server.
Authentication
Use the same rf_live_... API key you already use for the REST API (see Authentication), sent the same way:
Authorization: Bearer rf_live_...- No key supplied: only the documentation tools are available.
- Valid key supplied: documentation tools plus the conversation, template and messaging tools scoped to that key's WhatsApp phone number.
There is no separate MCP-specific credential and no OAuth flow to set up.
Documentation tools
| Tool | Purpose |
|---|---|
list_documentation | Lists every documentation page, grouped by category |
search_documentation | Searches page titles and summaries for a keyword |
get_documentation_page | Fetches the full content of one page by its slug |
Conversation tools
Read-only and not billed. Require a valid API key:
| Tool | Purpose |
|---|---|
list_conversation_numbers | List customer numbers, each with 24-hour window status and name |
get_conversation_history | Last 10 messages with one number, with time, sender and message text |
Template tools
Require a valid API key:
| Tool | Purpose |
|---|---|
list_templates | List every template with its approval status, quality score and structure - read-only, not billed |
get_template_status | Check one template's approval status by name, across every language variant - read-only, not billed |
create_template | Submit a new template for Meta approval - not billed itself, but requires the number's maintenance fee to be paid |
Messaging tools
Each of these performs a real, billed WhatsApp send and requires a valid API key:
| Tool | Purpose |
|---|---|
send_text_message | Plain text message |
send_template_message | Approved template, with variables |
send_media_message | Image, video, audio or document by link or media ID |
send_interactive_list_message | Interactive message with a selectable list |
send_interactive_buttons_message | Interactive message with up to 3 quick-reply buttons |
If the wallet balance is too low or the account maintenance fee for the number is unpaid, the tool call returns a clear "Payment required" error instead of failing silently - the same 402 behavior as the REST API (see Errors).