Ext Ops Panel
Open dashboard
Comparison

connector-namespaces vs wechat-webhooks

connector-namespaces is a plugin bundle for AI coding tools published by Azure. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). wechat-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
Marketplaceconnector-namespaceswechat-webhooks
Copilot CLI: github/awesome-copilot Listed
Version: 1.2.0
Forks (GitHub): 7
Stars (GitHub): 20
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 92
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

connector-namespaces vs wechat-webhooks
Factconnector-namespaceswechat-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)20 (worse)92 (better)
Forks (GitHub) (differs)7 (worse)16 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/azure/connectorsgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21

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

connector-namespaces

In its own words, on Copilot CLI: github/awesome-copilot:

Interactive GitHub Copilot canvas for discovering, connecting, and managing hosted MCP servers from an Azure Connector Namespace.

wechat-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify WeChat Pay (APIv3) webhook notifications. Use when setting up WeChat Pay webhook handlers, debugging Wechatpay-Signature RSA-SHA256 verification, decrypting the AEAD_AES_256_GCM encrypted resource, or handling payment and refund events like TRANSACTION.SUCCESS, REFUND.SUCCESS, and REFUND.CLOSED.

How to run each

connector-namespaces

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

wechat-webhooks As a Claude Code plugin

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

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

Neither one's marketplaces publish the settings it asks for.

What it can do: connector-namespaces · What it can do: wechat-webhooks · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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