replywizard-whatsapp-mcp 0.2.4 → 0.2.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +11 -8
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -40,10 +40,11 @@ extension** (the hub only sees tool arguments and results).
40
40
 
41
41
  ## Setup
42
42
 
43
- > **Recommended: the multi-agent connector.** Point your client at `rw-mcp-connector` (see
44
- > [Multiple AI assistants at once](#multiple-ai-assistants-at-once-daemon) below) so several assistants
45
- > can share one WhatsApp session. The single-client examples in this section still work but bind the
46
- > port directly — only one client at a time.
43
+ > **Multi-agent by default.** The `npx -y replywizard-whatsapp-mcp` config below runs the **connector**
44
+ > (the package's default bin), which auto-starts a shared local **daemon** — so several assistants
45
+ > (Claude Code + Cursor + Claude Desktop, …) can share one WhatsApp session at once, with no extra setup.
46
+ > See [Multiple AI assistants at once](#multiple-ai-assistants-at-once-daemon) for the architecture. Use
47
+ > the single-arg form above (not the older `-p <pkg> <bin>` form, which some clients fail to launch).
47
48
 
48
49
  Published to npm as [`replywizard-whatsapp-mcp`](https://www.npmjs.com/package/replywizard-whatsapp-mcp).
49
50
  You don't install anything by hand — your AI client runs it via `npx` (requires Node.js 18+).
@@ -73,13 +74,15 @@ claude mcp add replywizard -- npx -y replywizard-whatsapp-mcp
73
74
  `RW_MCP_PORT` is optional (defaults to `7869`); set it on both sides if you change it.
74
75
 
75
76
  > **Running from source instead?** Clone the repo, `cd mcp-host && npm install`, and point your
76
- > client at `node /absolute/path/to/mcp-host/src/index.js` rather than the `npx` command above.
77
+ > client at `node /absolute/path/to/mcp-host/src/connector.js` (multi-agent) — or
78
+ > `node .../src/index.js` for the legacy single-client, no-daemon hub.
77
79
 
78
80
  ## Multiple AI assistants at once (daemon)
79
81
 
80
- The `index.js` hub above binds the WebSocket port directly, so **only one AI client can use it at a
81
- time** (a second launch hits `EADDRINUSE`). To let several clients (Claude Code + Cursor + Claude
82
- Desktop, …) share one WhatsApp session, run the **daemon** instead:
82
+ This happens automatically with the `npx` config above: `replywizard-whatsapp-mcp` runs the connector,
83
+ which starts one shared daemon. (The legacy `index.js` hub — run directly via `node .../src/index.js` —
84
+ binds the WebSocket port itself, so **only one AI client can use it at a time**; a second launch hits
85
+ `EADDRINUSE`.) The daemon architecture:
83
86
 
84
87
  ```
85
88
  client A (HTTP) ─┐
package/package.json CHANGED
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "replywizard-whatsapp-mcp",
3
- "version": "0.2.4",
3
+ "version": "0.2.5",
4
4
  "description": "Local MCP server that exposes WhatsApp Web (read + value tools) to AI clients via the Reply Wizard Chrome extension.",
5
5
  "type": "module",
6
6
  "bin": {
7
- "replywizard-whatsapp-mcp": "src/index.js",
7
+ "replywizard-whatsapp-mcp": "src/connector.js",
8
8
  "rw-mcp-daemon": "src/daemon.js",
9
9
  "rw-mcp-connector": "src/connector.js"
10
10
  },