threads-webhooks vs TwitterAPIs
threads-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). TwitterAPIs is an MCP server published by TwitterAPIs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  TwitterAPIs | |
|---|---|---|
| Community marketplace hookdeck/webhook-skills | Listed Version: not stated Forks (GitHub): 17 Stars (GitHub): 99 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.28.1 Downloads/month (npm): 3 443 Downloads/week (npm): 200 Forks (GitHub): 3 Stars (GitHub): 6 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.28.1 Downloads/month (npm): 3 443 Downloads/week (npm): 200 Forks (GitHub): 3 Stars (GitHub): 6 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 | threads-webhooks | TwitterAPIs |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 99 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 17 (better) | 3 (worse) |
| Last release (differs) | Not published | 2026-11-09 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/hookdeck/webhook-skills | github.com/twitterapis/twitterapis-mcp |
| Changes in the last 7 days (differs) | 2 | 10 |
| First seen (differs) | 2026-11-06 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 401 |
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
threads-webhooks
Receive and verify Threads (Meta) webhooks. Use when setting up Threads webhook handlers, completing the GET hub.challenge handshake, debugging X-Hub-Signature-256 signature verification, or handling replies, mentions, publish, and delete notifications.
TwitterAPIs
Official MCP server for twitterapis.com. Twitter/X search, users, DMs, Grok, monitoring and writes.
How to run each
threads-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install threads-webhooks@webhook-skillsTwitterAPIs As a remote MCP server
claude mcp add --transport http twitterapis-mcp https://api.twitterapis.com/mcpRequires: TWITTERAPIS_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only TwitterAPIs 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
The marketplaces of threads-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: threads-webhooks · What it can do: TwitterAPIs · 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. 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.