What is ThingsBoard MCP Server?
ThingsBoard MCP Server is the IoT platform's own Spring Boot server that turns MCP tool calls into ThingsBoard REST API requests. It works against ThingsBoard Cloud, EU Cloud, self-hosted Community and Professional Editions, and ThingsBoard Edge, and covers devices, assets, customers, users, alarms, telemetry and attributes, entity relations, OTA firmware packages, Professional Edition entity groups, and a filtered entity data query language.
It is Apache-2.0, written in Java 17, shipped as the thingsboard/mcp Docker image or a JAR, and runs over stdio or SSE. The repository has about 99 stars; the latest release, v2.1.0, came out on 17 February 2026, with the last commit on 26 February 2026.
How to install ThingsBoard MCP Server
docker run -i --rm -e THINGSBOARD_URL -e THINGSBOARD_API_KEY thingsboard/mcpIs ThingsBoard MCP Server worth it?
Breadth comes from mapping the REST API closely. The server registers more than 120 tools in 10 groups: 11 for devices, 8 for assets, 9 for alarms, 11 for telemetry and attributes, 11 for OTA packages, 8 for relations, 7 for customers, 9 for users, 10 for Professional Edition entity groups, and 40 for entity data and count queries, including three guide tools that explain the query syntax to the model. Questions such as which devices of one type reported a temperature above a threshold in the last day become a single filtered query instead of a page of REST calls.
Tool count is also the first problem. Each group has an environment switch, and the README shows how to drop to about 50 tools for clients with small context windows by turning off entity queries, OTA, groups and users.
Write access is the larger issue, and there is no read-only switch. The same toolset deletes devices, users and relations, saves telemetry and attributes, returns device credentials, and assigns OTA firmware to a device or a whole device profile. Shared attributes and firmware assignments reach physical hardware, so the credential matters: an API key (ThingsBoard 4.3 and later) or a username and password for older versions, with whatever rights that user holds. A customer-level user with narrow permissions is a safer default than a tenant administrator.
Operationally it is conventional. Docker over stdio is the documented path; SSE mode binds to 127.0.0.1:8000 by default, and the README does not describe authentication on the SSE endpoint itself. The project has moved slowly since the 2.1.0 release in February 2026, with 4 open issues and pull requests at the time of checking.
Where it earns its place
An operations engineer monitoring 400 cold-chain sensors
Find which units breached a temperature limit overnight and acknowledge the alarms
Ask the agent to run an entity data query by device type with a telemetry filter, list the highest alarm severity per device, then acknowledge after review. Runs on any plan that holds the fleet; Startup at $399/month covers 500 devices.
A firmware lead at an industrial-sensor maker
Check which devices in a profile still lack the latest OTA package
Use countByDeviceProfileAndEmptyOtaPackage and getOtaPackagesByDeviceProfile to see the gap, then assign the package by hand or with explicit approval. Keep OTA tools disabled for everyday query sessions.
A solutions engineer preparing a customer demo
Populate a fresh tenant with sample devices, assets and telemetry
Have the agent create devices with createOrUpsertDevice, link them to assets with relations, and write generated time-series with saveEntityTelemetry. The free Cloud plan's 5 devices suit a small demo.
Before you commit
- Setup
- docker pull thingsboard/mcp, then add it to Claude Desktop, Claude Code, Cursor or VS Code with THINGSBOARD_URL and THINGSBOARD_API_KEY. A JAR and a Maven build from source (Java 17, Maven 3.6) are alternatives.
- Integrations
- ThingsBoard Cloud, EU Cloud, self-hosted CE and PE, and Edge over their REST APIs. Ten tool groups with THINGSBOARD_TOOLS_* switches; 40 tools in the entity query and guide group alone.
- Data and privacy
- Runs locally or in your own container and talks only to your ThingsBoard instance; telemetry and entity data go to your model provider. Tools can delete entities, write attributes, read device credentials and assign firmware.
- Cost at scale
- The server is free. ThingsBoard Cloud: Prototype $49/month for 50 devices, Pilot $149 for 100, Startup $399 for 500, Business $749 for 1,000, with extra devices at $0.30 each up to 5,000.
- Limits
- More than 120 tools by default can exceed client context limits; SSE defaults to 127.0.0.1:8000; API-key login needs ThingsBoard 4.3 or later, older versions use username and password refreshed every 1,800 seconds.
What’s good
- Official, Apache-2.0, maintained by ThingsBoard
- 120+ tools across devices, telemetry, alarms and OTA
- Per-group switches to cut the tool list to about 50
- Works with Cloud, self-hosted and Edge
What’s not
- No read-only mode; delete and firmware tools always on
- Can return device credentials to the model
- SSE endpoint authentication not documented
- No release since February 2026
Best for
IoT engineers and operations teams already on ThingsBoard who want to query fleets, triage alarms and inspect telemetry from an agent with a deliberately limited account.
ThingsBoard MCP Server alternatives
ThingsBoard MCP Server: common questions
- Is ThingsBoard MCP Server worth it?
- A thorough, vendor-built bridge from an agent to a ThingsBoard tenant, whose delete, attribute and firmware tools deserve a scoped account before anyone points it at production devices. We rate it 3.9 out of 5.
- How much does ThingsBoard MCP Server cost?
- Free (Apache-2.0). Needs a ThingsBoard instance: Cloud plans run from Free (5 devices) to Business at $749/month (1,000 devices), or self-host.
- What are the downsides of ThingsBoard MCP Server?
- No read-only mode; delete and firmware tools always on; can return device credentials to the model; sSE endpoint authentication not documented; no release since February 2026.
- Who is ThingsBoard MCP Server best for?
- IoT engineers and operations teams already on ThingsBoard who want to query fleets, triage alarms and inspect telemetry from an agent with a deliberately limited account.
- How much does ThingsBoard MCP Server cost for a team or in production?
- The server is free. ThingsBoard Cloud: Prototype $49/month for 50 devices, Pilot $149 for 100, Startup $399 for 500, Business $749 for 1,000, with extra devices at $0.30 each up to 5,000.
- Is ThingsBoard MCP Server safe for company data?
- Runs locally or in your own container and talks only to your ThingsBoard instance; telemetry and entity data go to your model provider. Tools can delete entities, write attributes, read device credentials and assign firmware.
- What are the best ThingsBoard MCP Server alternatives?
- The closest alternatives we have reviewed are Home Assistant MCP Server and Grafana MCP Server.
Answers checked Nov 6, 2026.