text-touch-builder vs Commune
text-touch-builder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑03.
text-touch-builder is a plugin bundle for AI coding tools published by DataSift. No marketplace we read lists it any more. Commune is an MCP server published by shanjai-raj. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Commune | |
|---|---|---|
| Community marketplace datasift-ty-personal/siftstack | Removed on 2026-11-03 Version: not stated Forks (GitHub): 23 Stars (GitHub): 23 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.9 Downloads/month (PyPI): 98 Downloads/week (PyPI): 31 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 | text-touch-builderno longer listed · | Commune |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 23 | 1 |
| Forks (GitHub) (differs) | 23 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (commune-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/datasift-ty-personal/siftstack | github.com/shanjai-raj/commune-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of text-touch-builder
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Find a texting assistant for your goals in AutoMessage's public catalog.
-
Send SMS and MMS messages, manage contacts, and configure messaging workflows using the Kudosity platform. This plugin enables Claude to create and send messages, manage contact…
-
Email, WhatsApp and Telegram for AI agents: send, campaigns, automations, contacts, agent inboxes.
-
Build and send email, SMS, and push straight from your AI agent.
-
Official Sent plugin for SMS, WhatsApp, RCS, scheduled template sends, Sender Profiles, SMS compliance, authorized feedback, contacts, analytics, API integration, webhooks…
-
Send RCS & SMS campaigns: templates, audiences, surveys, inbox replies, delivery webhooks.
What each says it does
text-touch-builder
Generate a four-text-touch SMS sequence for your hottest DataSift records, personalized per record and varied like cold email so messages never look mass-blasted.
Commune
Email and SMS MCP server for AI agents — 41 tools for inboxes, sending, search, and SMS.
How to run each
text-touch-builder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commune As a local MCP server: PyPI package
claude mcp add --env "COMMUNE_API_KEY=<YOUR_COMMUNE_API_KEY>" --transport stdio commune-mcp -- uvx commune-mcpRequires: COMMUNE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of text-touch-builder publish no settings it asks for, so we do not compare settings.
What it can do: text-touch-builder · What it can do: Commune · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.