Skip to content
WACRM.AI
Early access

wacrm-mcp: let an AI agent use WACRM

wacrm-mcp is a Node MCP server with five tools over the WACRM Core API: send a WhatsApp template, read a conversation, create a contact, watch order and message-status updates, and read the token wallet balance. It authenticates with a WACRM API key you supply as an environment variable, never a key typed into this site.

By the WACRM team Updated

Request Early Access See the Core API

Lives in the WACRM repository today — not published to npm or any package registry yet

5 tools, each a thin, direct translation to one existing, already-tested Core API call

Protocol: the official @modelcontextprotocol/sdk over stdio (initialize, tools/list, tools/call)

Auth: a scoped WACRM API key via the WACRM_API_KEY environment variable, sent only as Authorization: Bearer

No business logic in the server — scope checks, idempotent replay and wallet deduction all happen in the Core API

WACRM is not affiliated with or endorsed by Meta

What wacrm-mcp is for

An AI agent that already talks MCP can use these five tools the same way a person uses the WACRM Workspace inbox: send an approved template, catch up on a conversation, add a new contact, watch for order and delivery-status updates, and check how much of the token wallet is left. Every tool is a thin translation to one Core API call made with the caller's own scoped API key — the server never holds business logic, a policy decision, or a cache of its own.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO

Ask which tool fits your agent, or how to point an MCP client at the server.

WhatsApp +84 937 869 689 [email protected]

Tools

ToolCore API callScopeNotes
send_template POST /v1/messages (type: template) messages:send Always carries an Idempotency-Key — a retry with the same key never sends twice.
read_conversation GET /v1/contacts/{contact}/messages contacts:read Watermark pagination — pass back next_since_id to page forward.
create_contact POST /v1/contacts contacts:write Can answer 402 plan_limit_reached if the project's contact limit is used up.
notify_order POST /v1/webhook-endpoints wa_webhooks:write Subscribes the caller's own HTTPS endpoint to the message.status event — there is no separate order-notification route yet.
wallet_balance GET /v1/token-balance wallet:read No input — returns the project's current balance and usage this cycle.

Config

Point an MCP client at the server over stdio, with your own scoped key in the environment:

{
  "mcpServers": {
    "wacrm": {
      "command": "node",
      "args": ["/path/to/apps/mcp/src/index.mjs"],
      "env": {
        "WACRM_API_KEY": "sk_live_your_scoped_key",
        "WACRM_API_BASE": "https://api.wacrm.ai"
      }
    }
  }
}

What this is not

  • Not published to npm or any package registry yet — the package lives in this repository only.
  • Not a public repository — there is no public source link to point to for it today.
  • WACRM is not affiliated with or endorsed by Meta.
  • No wallet deduction or plan gating happens inside this server — that lives in the Core API itself.

Frequently asked questions

Is wacrm-mcp published to npm yet?

Not yet. The package lives inside the private WACRM repository today, with no publish configuration and no public GitHub repository. A public package release is planned.

How does wacrm-mcp authenticate?

With a WACRM API key you provide as the WACRM_API_KEY environment variable when you start the server. The key is sent only as the Authorization: Bearer header of each Core API request — never logged, and never echoed back in a tool result or error.

Does the MCP server add its own billing or scope checks?

No. wacrm-mcp has no business logic of its own: scope checks, idempotent replay and wallet deduction all happen inside the Core API behind the key you supply, exactly as they would for a direct API call.

What happens when a tool call fails?

The tool returns an error result carrying the Core API's own {code, message} — insufficient_scope, an invalid credential, a 404, a conflict, or a rate limit — never a silent empty result.

Is WACRM affiliated with Meta?

No. WACRM is an independent product built on the WhatsApp Business Platform and is not affiliated with or endorsed by Meta, on this page or anywhere else on wacrm.ai.

Sources

Related

Core API v1 reference

Learn more

Get a WACRM API key for your agent

Request early access to get a Workspace and mint a scoped API key for wacrm-mcp.

Request Early Access See the Core API