iotdb-mcp-server

Created By
JackieTien97a year ago
iotdb_mcp_server
Overview

what is iotdb-mcp-server?

The iotdb-mcp-server is a Model Context Protocol (MCP) server implementation for IoTDB, designed to provide AI assistants with a secure and structured way to explore and analyze databases.

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 the Claude Desktop's configuration file.

key features of iotdb-mcp-server?

  • List tables and resources in the database.
  • Read data from tables.
  • Execute SQL queries through a controlled interface.
  • Integration with Claude Desktop for enhanced functionality.

use cases of iotdb-mcp-server?

  1. Enabling AI assistants to interact with IoTDB databases securely.
  2. Facilitating data analysis and exploration for research purposes.
  3. Providing a structured way for applications to access database resources.

FAQ from iotdb-mcp-server?

  • What are the prerequisites for using the server?

You need Python with the uv package manager, IoTDB installation, and MCP server dependencies.

  • How do I configure the server for Claude Desktop?

You need to edit the configuration file located in the appropriate directory for your operating system and provide the necessary environment variables.

  • Is there any support for other database operations?

Currently, the server supports listing resources, reading data, and executing SQL queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackieTien97
Star
0
Language
Python
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