← Back to directory
W

wacrm MCP Server

Community
Drive your self-hosted wacrm WhatsApp CRM from Claude, Cursor, and other MCP clients.
Category
Collaboration #51 of 55
Stars
★ 2.5k Very popular
Transport
stdio (local process)
Runtime
Node.js
Credentials
API key / credential required
License
MIT
Last commit
36FMRS · D

This server offers a convenient integration for wacrm users with AI assistants, but attention to permissions and risk control is needed.

Strongest · Security and permissions 10/20 Weakest · Reliability 3/20

Reliability
3/20
Security and permissions
10/20
Maintenance
8/20
Documentation
8/20
Setup experience
7/20
Why each score
Reliability 3/20
A well-formed manifest is provided and describes a plausible stdio npm server, but no server source, tests, or CI workflow for the MCP server was supplied. There is no verifiable evidence that the init and tool-list handshake succeeds, or that declared tools match real behavior. The score is downgraded for missing executable evidence and committed tests; the static calibration cap is 12, and the evidence is well below that.
Security and permissions 10/20
No red-line issues were found. The API key is marked as secret, writes are disabled unless WACRM_ENABLE_WRITES=true, and broadcasts additionally require WACRM_ENABLE_BROADCASTS, which is a good least-privilege default. Deductions: there is no source to verify that tools actually enforce API key scopes, no confirmation flow for write/broadcast operations is documented, and there is no data-flow disclosure for external WhatsApp calls. This fits the 10-point band where main risks are visible but permissions/confirmation/scoping are incomplete.
Maintenance 8/20
The repository is not archived, has an MIT license, and the package version is 0.1.1. No release history, commit cadence, dependency-update evidence, or security-response channel was supplied; stars are treated as discovery signals only and add no points. The score is deducted for missing governance and versioning evidence.
Documentation 8/20
The README gives a product overview and points to docs/mcp.md and public API docs, and the manifest explains the environment variables. However, no MCP-specific documentation was supplied: no tool parameter reference, no scopes/limits, no cost guidance, and no troubleshooting section. The score is deducted for missing tool-level and troubleshooting documentation.
Setup experience 7/20
The npm identifier, stdio transport, and required environment variables are clearly declared, which gives a plausible setup path. But no MCP client configuration examples for Claude/Cursor, no prerequisites list, and no installation verification were included. The setup is plausible but unverified; the static calibration cap is 15, and missing execution evidence lowers the score to 7.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Teams or individuals using wacrm who want to increase CRM productivity via AI assistants
  • Developers who need self-hosting with full control over data and configuration

Not for

  • Users not using wacrm or WhatsApp Business API
  • Those requiring an official, upstream-maintained MCP server (this is community-maintained)

Required permissions

  • Requires an API key from the wacrm instance; scopes define allowed actions
  • Read-only by default; enabling WACRM_ENABLE_WRITES allows contact create/update and message sending
  • Enabling WACRM_ENABLE_BROADCASTS allows mass broadcasts

Risks and side effects

  • API key leakage could lead to unauthorized access or actions
  • With writes/broadcasts enabled, AI might execute unintended operations
  • Misconfiguration of the self-hosted instance may cause connection failures

Setup

Before you start

Runtime:Node.js

WACRM_BASE_URL required Base URL of your self-hosted wacrm instance, e.g. https://crm.example.com.
WACRM_API_KEY requiredsecret API key generated in the CRM under Settings → API keys; its scopes decide what is allowed.
Other optional settings (2)
WACRM_ENABLE_WRITES optional Set to true to expose contact create/update and message sending; read-only when unset.
WACRM_ENABLE_BROADCASTS optional Set to true to expose the mass-broadcast tool; requires WACRM_ENABLE_WRITES.

Install the wacrm-mcp npm package and configure environment variables: WACRM_BASE_URL (base URL of your wacrm instance), WACRM_API_KEY (API key from Settings), WACRM_ENABLE_WRITES (set to true to enable writes), WACRM_ENABLE_BROADCASTS (set to true to enable broadcasts, requires writes).

Check that it works

Confirm wacrm tools appear in your MCP client's tool list, then ask a read-only question such as listing contacts — returning real data from your wacrm instance proves the connection works.

Troubleshooting

  1. Check that WACRM_BASE_URL is reachable from the MCP client
  2. Verify the API key is valid and has required scopes
  3. Ensure environment variables are set correctly, especially WACRM_ENABLE_WRITES when enabling writes

Things to try

Once connected, you can ask your AI assistant things like:

  • List all contacts in my wacrm CRM
  • Show the most recent open conversations and who they are assigned to
  • Tag the customer John as vip
  • Send a WhatsApp reply to the customer's latest message

Use cases

View contacts, conversations, and pipeline data from AI assistants
AI-drafted replies (with writes enabled)
Run no-code automations or broadcasts (with appropriate permissions)

Supported clients

Claude Desktop
Cursor

Listed from the project's documentation, not tested by this site.

Overview

This MCP server allows AI assistants like Claude and Cursor to interact with a self-hosted wacrm instance, a CRM template for WhatsApp providing shared inbox, contacts, sales pipelines, broadcasts, and no-code automations. It is read-only by default, with optional write and broadcast features.

Similar servers

Source revision 27c6bdf43633 Data synced 2026-10-12 Read the FMRS scoring method