Thingsboard MCP Server

Thingsboard MCP server exists for a simple reason — assistants are far more useful when they can act on Thingsboard directly instead of describing what you should do. Type-safe TypeScript client for the ThingsBoard REST API with Zod v4 runtime validation.

What you get

Generated from the official ThingsBoard OpenAPI 3.1 spec using @hey-api/openapi-ts.

• Full ThingsBoard REST API coverage, generated from a TB Professional Edition spec (PE is a superset of CE — CE-only consumers will see SDK functions for PE-only endpoints that 404 on their server)
• login() / logout() helpers (not in the OpenAPI spec, provided manually)
• TypeScript types for all endpoints, request bodies, and responses
• Zod schemas for runtime validation at API boundaries
• Native fetch — works in Node.js 20+, Bun, Deno, and browsers
• Tree-shakeable — import only the endpoints you use for minimal bundle size

What the assistant can call

Once Thingsboard is connected, these are the calls the assistant has available:

• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: THINGSBOARD_SPEC_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 20+ - pnpm 8+

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Thingsboard's toolset — Prerequisites, Setup — is a fair guide to whether it matches your workflow. It is maintained by rafael.gutierrez.enerlab; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Thingsboard's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the thingsboard mcp server does with a few real requests.