IoTDB MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is IoTDB MCP Server?

IoTDB MCP Server is a Model Context Protocol (MCP) server implementation that provides database interaction and business intelligence capabilities through IoTDB, enabling users to run SQL queries.

how to use IoTDB MCP Server?

To use the IoTDB MCP Server, clone the repository, set up a virtual environment, install dependencies, and configure the server in Claude Desktop's configuration file.

key features of IoTDB MCP Server?

  • Execute SQL SELECT queries to read data from the database.
  • List all tables in the database.
  • View schema information for specific tables.

use cases of IoTDB MCP Server?

  1. Running SQL queries for data analysis.
  2. Integrating with business intelligence tools for data visualization.
  3. Managing and querying IoT data efficiently.

FAQ from IoTDB MCP Server?

  • What are the prerequisites for using IoTDB MCP Server?

You need Python with the uv package manager and IoTDB installed.

  • How do I configure the server?

You need to edit the Claude Desktop configuration file with the server details.

  • Is there any support for other SQL commands?

Currently, the server primarily supports SELECT queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
Apache-2.0 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)

a day ago