tdengine-mcp-server

Provides an MCP (Model Context Protocol) server integration for TDengine (open-source time-series database), enabling AI agents to interact with TDengine via MCP tools.

Evaluated Apr 04, 2026 (20d ago)
Homepage ↗ Infrastructure mcp tdengine time-series database agent-tools
⚙ Agent Friendliness
37
/ 100
Can an agent use this?
🔒 Security
40
/ 100
Is it safe for agents?
⚡ Reliability
26
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
35
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

TLS Enforcement
60
Auth Strength
40
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
40

No concrete repository/manifests were provided here to verify TLS-only connections, credential handling, or dependency health. Treat DB credentials as highly sensitive; the MCP layer can increase blast radius if it allows broad query capabilities.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
30
Error Recovery
40
AF Security Reliability

Use Cases

  • • Letting AI agents query TDengine time-series data using MCP tool calls
  • • Building agent workflows that analyze telemetry/metrics stored in TDengine
  • • Abstracting TDengine access behind an MCP interface for LLM-driven operations

Not For

  • • Direct end-user database access without an agent/MCP runtime
  • • Production-grade database administration unless MCP server is verified for security, correctness, and operational hardening
  • • Environments requiring strict enterprise compliance guarantees without documented controls

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanisms could be verified from the provided information. MCP servers commonly accept DB credentials (or environment variables), but specifics are not available here.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; likely open-source tooling.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ If tool calls can execute arbitrary SQL, agents may generate unsafe or overly expensive queries
  • ⚠ Time-series queries may be sensitive to time range/window parameters; agents might omit bounds leading to large scans
  • ⚠ Without clear schema/tool parameter definitions, agents may hallucinate table/column names

Alternatives

Use TDengine native drivers/APIs directly from your application (avoid MCP layer) Build a small custom tool layer (REST/SDK wrapper) that exposes only safe, parameterized queries to your agent framework If available, use other DB-specific MCP servers or generic SQL MCP integrations

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for tdengine-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered