WhatsApp MCP by TimelinesAI vs Kaption WhatsApp
WhatsApp MCP by TimelinesAI is an MCP server published by InitechSoftware. Marketplaces we read that list it: 1 (Official MCP Registry). Kaption WhatsApp is an MCP server published by Kaption-AI. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  WhatsApp MCP by TimelinesAI |  Kaption WhatsApp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 2 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.5.11 Downloads/month (npm): 1 315 Downloads/week (npm): 391 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.5.12 Downloads/month (npm): 1 315 Downloads/week (npm): 391 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | WhatsApp MCP by TimelinesAI | Kaption WhatsApp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 4 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Remote server (mcp.services.timelines.ai/mcp) | On your machine (@kaptionai/mcp-extension) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | BUSL-1.1 |
| Repository (differs) | github.com/initechsoftware/whatsapp-mcp-by-timelinesai | github.com/kaption-ai/mcp-extension |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
WhatsApp MCP by TimelinesAI
Ask questions across your WhatsApp inbox from Claude, ChatGPT, Cursor or any MCP client.
Kaption WhatsApp
Read and manage your WhatsApp conversations through the KaptionAI browser extension.
How to run each
WhatsApp MCP by TimelinesAI As a remote MCP server
claude mcp add --transport http whatsapp-mcp-by-timelinesai https://mcp.services.timelines.ai/mcpKaption WhatsApp As a local MCP server: npm package
claude mcp add --transport stdio mcp-extension -- npx -y @kaptionai/mcp-extensionCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only WhatsApp MCP by TimelinesAI has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: WhatsApp MCP by TimelinesAI · What it can do: Kaption WhatsApp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.