ThingsBoard vs meraki-webhooks
ThingsBoard is an MCP server published by thingsboard. Marketplaces we read that list it: 1 (Docker MCP Catalog). meraki-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-21. 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 |  ThingsBoard | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b6733d2cfbb9 Forks (GitHub): 28 Pulls (Docker Hub): 9 966 Stars (Docker Hub): 0 Stars (GitHub): 98 Not marked · First seen |
Not listed |
| Community marketplace hookdeck/webhook-skills | Not listed | Listed Version: not stated No figure published 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 | ThingsBoard | meraki-webhooks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 98 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 9 966 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 28 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/thingsboard) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 62 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/thingsboard/thingsboard-mcp | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-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
ThingsBoard
Connect your AI workflows to the ThingsBoard IoT Platform through this MCP server. Enables LLMs to query device telemetry, manage IoT entities (devices, assets, customers), and analyze sensor data - all through natural language. Perfect for building AI-powered IoT monitoring, predictive maintenance, and automated device management workflows. Supports both ThingsBoard Community Edition and Professional Edition.
meraki-webhooks
Receive and verify Cisco Meraki Dashboard webhook alerts. Use when setting up Meraki webhook handlers, validating the sharedSecret, or handling alert events like motion_alert, settings_changed, sensor_alert, or stopped_reporting.
How to run each
ThingsBoard As a local MCP server: Docker image
claude mcp add --env "THINGSBOARD_PASSWORD=<YOUR_THINGSBOARD_PASSWORD>" --env "THINGSBOARD_USERNAME=<YOUR_THINGSBOARD_USERNAME>" --transport stdio thingsboard -- docker run -i --rm -e THINGSBOARD_PASSWORD -e THINGSBOARD_USERNAME mcp/thingsboardRequires: THINGSBOARD_PASSWORD (secret), THINGSBOARD_USERNAME (secret)
meraki-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install meraki-webhooks@webhook-skillsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of meraki-webhooks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of meraki-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: ThingsBoard · What it can do: meraki-webhooks · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.