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-dataA | 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. |
| query-dataA | Execute a Flux query inside an organization to inspect measurement schemas, run aggregations, or validate recently written data. |
| create-bucketB | Provision a new bucket under an organization so that subsequent write-data calls have a destination. |
| create-orgA | 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 targets a distinct operation: organization creation, bucket creation, data writing, and querying. There is no overlap in functionality.
All tool names follow a consistent verb-noun pattern with hyphens (create-bucket, create-org, query-data, write-data).
With 4 tools, the server is well-scoped for basic InfluxDB operations, though it is on the smaller side.
The set lacks read, update, and delete operations for organizations and buckets, which are common needs when managing an InfluxDB instance. This could lead to agent failures.