Ext Ops Panel
Open dashboard
Comparison

twitter-webhooks vs X-Use - X (Twitter) MCP Server

twitter-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). X-Use - X (Twitter) MCP Server is an MCP server published by ihuzaifashoukat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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

Where each is published
Marketplacetwitter-webhooksX-Use - X (Twitter) MCP Server
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 94
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.2.0
Downloads/month (PyPI): 192
Downloads/week (PyPI): 214
Forks (GitHub): 32
Stars (GitHub): 178
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

twitter-webhooks vs X-Use - X (Twitter) MCP Server
Facttwitter-webhooksX-Use - X (Twitter) MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)94 (worse)178 (better)
Forks (GitHub) (differs)16 (worse)32 (better)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleOn your machine (x-use-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/ihuzaifashoukat/x-use
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-10-11

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

twitter-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Twitter/X Account Activity API webhooks. Use when setting up X (Twitter) webhook handlers, debugging the x-twitter-webhooks-signature HMAC-SHA256 check, answering the CRC (Challenge-Response Check) crc_token request, or handling events like tweet_create_events, favorite_events, follow_events, and direct_message_events.

X-Use - X (Twitter) MCP Server

In its own words, on Official MCP Registry:

Research X (Twitter), read inboxes and review publishing through MCP. No X API key required.

How to run each

twitter-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install twitter-webhooks@webhook-skills

X-Use - X (Twitter) MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio x-use -- uvx x-use-mcp

Requires: OPENAI_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 twitter-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: twitter-webhooks · What it can do: X-Use - X (Twitter) MCP Server · 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.

Where the data comes from: how the catalog is built