Ext Ops Panel
Open dashboard
Comparison

ThingsBoard vs net.vybit/mcp-server

ThingsBoard is an MCP server published by thingsboard. Marketplaces we read that list it: 1 (Docker MCP Catalog). net.vybit/mcp-server is an MCP server published by vybit.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceThingsBoardnet.vybit/mcp-server
Docker MCP Catalog Listed
Version: sha256:b6733d2cfbb9
Forks (GitHub): 28
Pulls (Docker Hub): 9 875
Stars (Docker Hub): 0
Stars (GitHub): 98
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.10.0
Forks (GitHub): 0
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

ThingsBoard vs net.vybit/mcp-server
FactThingsBoardnet.vybit/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)98 (better)1 (worse)
Pulls (Docker Hub) (differs)9 875No figure on Docker Hub
Forks (GitHub) (differs)28 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/thingsboard)Remote server (api.vybit.net/v1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)62Not published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/thingsboard/thingsboard-mcpgithub.com/flatirontek/vybit-sdk
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

In its own words, on Docker MCP Catalog:

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.

net.vybit/mcp-server

In its own words, on Official MCP Registry:

Push notifications with personalized sounds - manage and trigger your vybits via MCP

How to run each

ThingsBoard As a local MCP server: Docker image

Claude Code
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/thingsboard

Requires: THINGSBOARD_PASSWORD (secret), THINGSBOARD_USERNAME (secret)

net.vybit/mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http net-vybit-mcp-server https://api.vybit.net/v1/mcp

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

Tools each declares

The marketplaces of net.vybit/mcp-server publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of net.vybit/mcp-server publish no settings it asks for, so we do not compare settings.

What it can do: ThingsBoard · What it can do: net.vybit/mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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