Thingsboard MCP Server

Created By
AnyContext-aia year ago
Thingsboard MCP Server for using Thingsboard Data as context in LLM tools
Overview

What is Thingsboard MCP Server?

Thingsboard MCP Server is a server designed to utilize Thingsboard Data as context in Large Language Model (LLM) tools, enabling enhanced data-driven applications.

How to use Thingsboard MCP Server?

To use the Thingsboard MCP Server, set up your environment by following the installation instructions for your operating system, configure the necessary environment variables, install dependencies, and run the server.

Key features of Thingsboard MCP Server?

  • Integration with Thingsboard for data context in LLM tools
  • Support for virtual environments to manage dependencies
  • Easy setup process for both Windows and Linux users

Use cases of Thingsboard MCP Server?

  1. Enhancing LLM applications with real-time data from Thingsboard.
  2. Building data-driven AI applications that require contextual information.
  3. Facilitating research and development in AI by providing a robust data backend.

FAQ from Thingsboard MCP Server?

  • What is Thingsboard?

Thingsboard is an open-source IoT platform for data collection, processing, visualization, and device management.

  • Is Thingsboard MCP Server free to use?

Yes! Thingsboard MCP Server is open-source and free to use.

  • What programming languages are supported?

The server is primarily built using Python, and it supports any language that can interact with its API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AnyContext-ai
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago