IoTDB MCP Server

Created By
apachea year ago
Apache IoTDB MCP Server
Overview

what is IoTDB MCP Server?

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

how to use IoTDB MCP Server?

To use the IoTDB MCP Server, clone the repository from GitHub, set up a virtual environment, install the necessary dependencies, and configure the server in the 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 to retrieve data from IoTDB.
  2. Analyzing database schemas for better data management.
  3. Integrating with business intelligence tools for data analysis.

FAQ from IoTDB MCP Server?

  • What are the prerequisites for using IoTDB MCP Server?

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

  • How do I configure the MCP server?

You need to edit the Claude Desktop's configuration file to include the MCP server settings.

  • 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
apache
Star
16
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago