Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.wazzapi.com/llms.txt

Use this file to discover all available pages before exploring further.

​
WazzAPI MCP

WazzAPI MCP plugs the WazzAPI platform directly into your LLM or coding agent so you can work with messaging data in natural language. Use it to:
  • send WhatsApp messages from an agent workflow
  • inspect device status and delivery activity
  • search message history and number status faster
  • debug webhook and messaging flows without building custom tooling first
WazzAPI MCP is ideal for developer tools and AI agents. For regular server-to-server application traffic, keep using the REST API and SDKs.

​
What it helps with

Send Messages

Trigger message sends from natural-language prompts inside your MCP-compatible agent.

Instrument Your App

Inspect delivery events, webhook activity, and messaging behavior without bouncing between tools.

Search Things

Ask for device state, delivery receipts, and message activity in plain English.

​
Server details

Use the hosted MCP endpoint: 
https://mcp.wazzapi.com/mcp
Authenticate with your WazzAPI API token using the header below: 
wazzapi-api-key: YOUR_API_TOKEN
Use a server-side token only. Never place MCP credentials in public client apps or shared browser sessions.

​
Claude Code setup

Open a terminal and run: 
claude mcp add --transport http wazzapi "https://mcp.wazzapi.com/mcp" --header "wazzapi-api-key=<YOUR_API_TOKEN>"
After the server is added, Claude Code can connect to your WazzAPI account automatically. If needed, manually authenticate from within Claude using /mcp.

​
Other MCP-compatible agents

The MCP landing page lists support targets including:
  • Claude Code
  • Cursor
  • VS Code
  • Windsurf
  • Zed
  • Warp
  • Gemini CLI
  • OpenCode
If your client supports remote MCP over HTTP, use the same hosted endpoint and header:
  • URL: https://mcp.wazzapi.com/mcp
  • Header: wazzapi-api-key: YOUR_API_TOKEN
If your client uses a JSON config file or UI form, map those values into its MCP server settings.

​
Path constraints

You can scope the MCP session to a specific workspace directly in the URL path: 
https://mcp.wazzapi.com/mcp/:workspace
Use this when you want the session restricted to one workspace context.

​
Agent mode

WazzAPI MCP also supports an agent mode that exposes a single use_wazzapi tool instead of individual skills. 
https://mcp.wazzapi.com/mcp?agent=1
You can combine it with a workspace-constrained session: 
https://mcp.wazzapi.com/mcp/:workspace?agent=1
According to the live MCP page, agent mode reduces visible tool surface area but can approximately double response time because requests pass through an embedded AI layer.

​
Authentication tips

WazzAPI MCP uses a dedicated request header instead of the REST API’s Bearer token format:
  • REST API → Authorization: Bearer YOUR_API_KEY
  • MCP → wazzapi-api-key: YOUR_API_TOKEN
If an MCP client reports authentication failures, double-check that:
  • the token belongs to the correct WazzAPI workspace
  • the header name is exactly wazzapi-api-key
  • the server URL is https://mcp.wazzapi.com/mcp

​
Try it live

You can explore the MCP experience from the hosted WazzAPI flow here:
  • https://wazzapi.com/mcp
  • https://app.wazzapi.com/

Authentication

Learn when to use Bearer API keys and when MCP uses a custom header.

API Reference

Use the REST API directly when you need deterministic backend integrations.

Python SDK

Use the typed Python client for application integrations outside MCP.

Node.js SDK

Use the official Node.js SDK for server-side automation and product code.