Model Context Protocol
Give your agent 129 messaging tools
One line of config connects Claude Code, Codex, Cursor or ChatGPT to a real messaging account. No wrapper functions to write, no tool schemas to maintain, no per-message billing to model.
Terminal
$ claude mcp add --transport http waapi \ https://waapi.app/mcp/waapi \ --header "Authorization: Bearer $WAAPI_TOKEN"
~/.codex/config.toml
[mcp_servers.waapi] url = "https://waapi.app/mcp/waapi" headers = { Authorization = "Bearer $WAAPI_TOKEN" }
ChatGPT (Team / Enterprise)
Settings → Connectors → Add custom connector Name WaAPI URL https://waapi.app/mcp/waapi Auth Bearer token: $WAAPI_TOKEN
~/.cursor/mcp.json
{
"mcpServers": {
"waapi": {
"url": "https://waapi.app/mcp/waapi",
"headers": {
"Authorization": "Bearer $WAAPI_TOKEN"
}
}
}
}
What the agent can actually reach
Not a send-message wrapper. The full surface of the API is exposed as individual tools, so an agent can read a conversation, decide, and act without you writing the intermediate steps.
25
Messages
22
Chats
16
Client
16
Contacts
15
Groups
8
Communities
7
Business profile
6
Instances
6
Channels
5
Stories
3
Labels
129 tools in total, counted from the server definition rather than estimated.
Why this beats a function wrapper
The schema is the contract
Each tool declares its own parameters, so the agent gets a typed description instead of guessing at an HTTP body. Mis-shaped calls fail at the boundary, not three steps later.
Read, then act
Fetching chats, contacts and group members are tools in their own right. An agent can look up who it is talking to before replying, in one session, without a retrieval layer you maintain.
Agents are chatty; billing is not
An agent loop can fire dozens of calls to resolve one question. Billing is a flat rate per connected account, so exploratory tool use does not turn into a line item.
MCP questions
Setup, transport and what an agent is allowed to do.
-
Anything that speaks the Model Context Protocol over HTTP — Claude Code, Codex, Cursor and ChatGPT are the ones we document. The server is a standard remote MCP endpoint, so a client we have not listed will still connect.
-
With the same bearer token as the REST API. One token covers the MCP server, the n8n node and both PHP packages, so nothing extra is issued or rotated separately.
-
Scope it with the token you hand over, and point the agent at a dedicated connected account rather than your main one. An agent with a token can use every tool that token permits.
-
Not on our side. Pricing is per connected account per month with unlimited messages, so the number of tool calls an agent makes while reasoning does not change the bill.
-
Yes. The tools act on a real linked account, so connect one in the dashboard and scan the code before pointing an agent at it. The free trial is enough to try the whole flow.
Point an agent at it
Connect an account, copy one line of config, and your agent has 129 tools.