Skip to main content
Glama
InfluxDB MCP Server

InfluxDB MCP Server

by idoru

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
INFLUXDB_ORGNoDefault organization name for certain operations
INFLUXDB_URLNoURL of the InfluxDB instancehttp://localhost:8086
INFLUXDB_TOKENYesAuthentication 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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription
flux-query-examples
line-protocol-guide

Resources

Contextual data attached and managed by the client

NameDescription
orgs
buckets

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency5/5

All four names follow the same lowercase hyphenated verb_noun convention (query-data, write-data, create-bucket, create-org). The pattern is fully predictable.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessOutdated data