InfluxDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFLUXDB_ORG | No | Default organization name for certain operations | |
| INFLUXDB_URL | No | URL of the InfluxDB instance | http://localhost:8086 |
| INFLUXDB_TOKEN | Yes | Authentication token for the InfluxDB API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write-dataB | Stream newline-delimited line protocol records into a bucket. Use this after composing measurements so the LLM can insert real telemetry, optionally controlling timestamp precision. Default org: "my-organization". |
| query-dataA | Execute a Flux query inside an organization to inspect measurement schemas, run aggregations, or validate recently written data. Default org: "my-organization". |
| create-bucketA | Provision a new bucket under an organization so that subsequent write-data calls have a destination. |
| create-orgB | Create a brand-new organization to isolate users or projects before generating buckets and tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| flux-query-examples | |
| line-protocol-guide |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| orgs | |
| buckets |
TDQS
Scored across 4 tools
Each tool maps to a distinct resource and action: query-data reads, write-data ingests, create-bucket provisions storage, and create-org provisions a top-level container. There is no plausible way to confuse these operations with one another.
All four names follow the same lowercase hyphenated verb_noun convention (query-data, write-data, create-bucket, create-org). The pattern is fully predictable.
Four tools is at the thin end of the acceptable range but each one earns its place in the core write/query workflow. A slightly larger surface (listing/cleanup) would round out the set.
The core read/write path plus resource creation is covered, but there are no list or delete operations for buckets or orgs, leaving lifecycle gaps. The create-org description mentions tokens, yet no token tooling exists, creating a dead end.