Enterprise DNA
M MCP Servers Developer low

thingsboard/thingsboard-mcp

by Various

πŸŽ–οΈ β˜• ☁️ 🏠 🍎 πŸͺŸ 🐧 - The ThingsBoard MCP Server provides a natural language interface for LLMs and AI agents to interact with your ThingsBoard IoT platform.

T

MCP

thingsboard/thingsboard-mcp

Added 1 June 2026

Overview

The ThingsBoard MCP Server implements the Model Context Protocol to provide a natural language interface for large language models and AI agents. It enables them to interact with the ThingsBoard IoT platform by translating LLM requests into platform API calls.

Best for

Best for
Developers building AI assistants that need to query or manage a ThingsBoard IoT deployment

Use cases

  • Letting an LLM query device telemetry data from ThingsBoard
  • Allowing AI agents to manage IoT dashboards and alarms via natural language
  • Enabling conversational interfaces for ThingsBoard platform administration

Notes

The ThingsBoard MCP Server implements the Model Context Protocol to provide a natural language interface for large language models and AI agents. It enables them to interact with the ThingsBoard IoT platform by translating LLM requests into platform API calls.

96 stars on GitHub. Last updated 2026-03-16. Licensed Apache-2.0.

Use cases

  • Letting an LLM query device telemetry data from ThingsBoard
  • Allowing AI agents to manage IoT dashboards and alarms via natural language
  • Enabling conversational interfaces for ThingsBoard platform administration

Pros

  • Bridges LLMs directly to ThingsBoard without custom integration code
  • Uses the open MCP standard, making it compatible with various LLM hosts
  • Written in Java, aligning with ThingsBoard’s backend language

Cons

  • Requires a running ThingsBoard instance to be useful
  • Dependent on the MCP protocol ecosystem, which is still evolving
  • Limited to functionality exposed via ThingsBoard’s REST API

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Bridges LLMs directly to ThingsBoard without custom integration code
  • Uses the open MCP standard, making it compatible with various LLM hosts
  • Written in Java, aligning with ThingsBoard's backend language

Cons

  • Requires a running ThingsBoard instance to be useful
  • Dependent on the MCP protocol ecosystem, which is still evolving
  • Limited to functionality exposed via ThingsBoard's REST API