Ext Ops Panel
Open dashboard
Comparison

gorgias-webhooks vs Openhook

gorgias-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Openhook is an MCP server published by openhook-dev. 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
Marketplacegorgias-webhooksOpenhook
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
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

gorgias-webhooks vs Openhook
Factgorgias-webhooksOpenhook
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (openhook.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/openhook-dev/openhook-inbox
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-10-13
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

gorgias-webhooks

In its own words, on Community GitHub marketplaces:

Receive and authenticate Gorgias HTTP integration webhooks. Use when setting up a Gorgias webhook handler for ticket events (ticket-created, ticket-updated, ticket-message-created, ticket-status-updated and other triggers), when building the user-defined request body template with variables like {{ticket.id}}, or when debugging the shared-secret header check. Gorgias does not sign HTTP integration requests: there is no signature header or HMAC, and the request body does not say which trigger fired unless you put the event name in the template yourself.

Openhook

In its own words, on Official MCP Registry:

Webhook, email and DNS inboxes for AI agents to capture callbacks and test integrations.

How to run each

gorgias-webhooks As a Claude Code plugin

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

Openhook As a remote MCP server

Claude Code
claude mcp add --transport http openhook-inbox https://openhook.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Openhook 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: gorgias-webhooks · What it can do: Openhook · 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