Lemma Telepath vs Kaption WhatsApp
Lemma Telepath is an MCP server published by lemma.company. 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-11-07. 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 |  Lemma Telepath |  Kaption WhatsApp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published 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.16 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 | Lemma Telepath | Kaption WhatsApp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | Remote server (telepath.lemma.company/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) | Not stated | github.com/kaption-ai/mcp-extension |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 404 | 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
Lemma Telepath
Search, read and reply to your Telegram Business chats, transcribed voice included.
Kaption WhatsApp
Read and manage your WhatsApp conversations through the KaptionAI browser extension.
How to run each
Lemma Telepath As a remote MCP server
claude mcp add --transport http telepath https://telepath.lemma.company/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 Lemma Telepath 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: Lemma Telepath · 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.