query-data is described as the way to validate recently written data, so write, read back, correct is one loop in one conversation rather than a trip to another tool. The surface stops there: four tools, no deletes, no task or dashboard management, and no way to list what buckets already exist. This is a data-in and data-out server, and the provisioning tools are there so the first write has somewhere to go.
A four-tool InfluxDB client covering the write path, Flux queries, and the organization and bucket provisioning those depend on.
- Newline-delimited line protocol streamed into a named bucket, with timestamp precision set per call
- Flux queries run inside an organization, for inspecting measurement schemas, running aggregations, or checking what a write actually stored
- Bucket creation with a retentionPeriodSeconds, so a destination exists before the first write
- Organization creation, to keep separate projects or users on their own buckets and tokens
INFLUXDB_URL for the instance, INFLUXDB_TOKEN with rights to write and to create buckets and organizations, and INFLUXDB_ORG as the organization queries run inside. MIT licensed.
One command plus a key — INFLUXDB_TOKEN=your_token npx influxdb-mcp-server, then supply credentials