Back to MCP Directory
Influxdb
Model Context Protocol moderate risk

Influxdb

Exposes InfluxDB v2 functionality (query, write, manage) via the Model Context Protocol, enabling AI agents to interact with time-series data.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readwriteexecadmin

Quickstart

Install

npx -y @smithery/cli install @idoru/influxdb-mcp-server --client claude

Config

{
  "mcpServers": {
    "influxdb": {
      "command": "npx",
      "args": ["influxdb-mcp-server"],
      "env": {
        "INFLUXDB_TOKEN": "your_token",
        "INFLUXDB_URL": "http://localhost:8086",
        "INFLUXDB_ORG": "your_org"
      }
    }
  }
}

Exposed MCP Tools (4)

moderate
write-data

Writes time-series data to InfluxDB in line protocol format.

Allows writing data to InfluxDB, potentially overwriting existing data.

safe
query-data

Executes Flux queries against InfluxDB and returns the results.

Read-only operation, no data modification.

moderate
create-bucket

Creates a new bucket in InfluxDB for storing time-series data.

Creates new buckets, which could consume resources and affect performance.

moderate
create-org

Creates a new organization in InfluxDB.

Creates new organizations, which could affect resource allocation and access control.

Safety Assessment

This MCP server provides access to InfluxDB, which can be risky if not configured correctly. It's safe to use for read-only operations and data analysis in a controlled environment. However, write and delete operations should be carefully monitored and restricted to authorized agents to prevent data loss or security breaches.

  • Requires InfluxDB token for authentication.
  • Clear separation of concerns in code structure.
  • Includes integration tests for functionality.
  • Uses InfluxDB OSS API v2, which has built-in security features.
  • Allows write and delete operations on InfluxDB data.
  • Relies on environment variables for sensitive information (token).
  • No explicit sandboxing or RBAC mechanisms within the MCP server itself.
  • Potential for data corruption or unauthorized access if token is compromised.