influxdb3_mcp_server

This MCP server provides a suite of InfluxDB 3 integration tools accessible via the MCP protocol. It exposes actions such as loading a custom database context, listing databases, writing data with InfluxDB line protocol, executing queries, managing tokens, and inspecting health status. The available tools are designed to work across InfluxDB 3 flavors (Core, Enterprise, Cloud Serverless, Cloud Dedicated, and Clustered), with some capabilities gated by edition (for example admin and token management features).

To use the server, run it with Node.js (as demonstrated in the setup guide) and configure an MCP client to talk to the running MCP server. In your MCP client configuration (the mcp.json you provide to the client), point the server at the node process started by the command above. The example configuration in the README illustrates using command: "node" with the path to the built index.js and environment variables for the InfluxDB connection. Once running, you can call tools like load_database_context, get_help, write_line_protocol, create_database, list_databases, health_check, and more. Depending on your InfluxDB deployment, you may access cloud-dedicated, clustered, or serverless capabilities via the corresponding prompts and tool endpoints.

Typical workflow:

• Start the MCP server via your preferred method.
• Configure your MCP client to point to the server (using the node-based built server path and necessary InfluxDB credentials).
• Use the available tools to manage databases, write data, query data, and monitor health.

Prerequisites:

• InfluxDB 3 instance (URL and token for Core/Enterprise or cluster details for Cloud variants)
• Node.js v18+ and npm v9+
• Docker (optional for Docker-based setup)

Installation steps:

1. Install dependencies

npm install

2. Build the MCP server (produces the build/index.js used by the Node runner)

npm run build

3. Run the server (example)

node /path/to/influxdb3_mcp_server/build/index.js

4. Prepare your MCP client configuration to point at the running server, for example:

{
  "mcpServers": {
    "influxdb3": {
      "command": "node",
      "args": ["/path/to/influxdb3_mcp_server/build/index.js"],
      "env": {
        "INFLUX_DB_INSTANCE_URL": "http://localhost:8181/",
        "INFLUX_DB_TOKEN": "<YOUR_TOKEN>",
        "INFLUX_DB_PRODUCT_TYPE": "core"
      }
    }
  }
}

Notes:

• If you prefer Docker, you can containerize the server following your organization’s conventions and expose the same environment variables inside the container.
• The exact paths and environment values should be replaced with your real InfluxDB deployment details.

Tips and common considerations:

• Ensure INFLUX_DB_INSTANCE_URL and INFLUX_DB_TOKEN are correctly set for your InfluxDB 3 instance. Different product types (core, enterprise, cloud-serverless, cloud-dedicated, clustered) require appropriate tokens and URLs.
• Admin and token management features (create_admin_token, list_admin_tokens, cloud_*, etc.) may be restricted to Core/Enterprise or Cloud variants; verify your edition supports the desired tools.
• For local development, you can use npm run build to prepare the server and then point your MCP client to the built index.js.
• If you encounter connectivity issues, check the health_check tool and ensure the InfluxDB instance URL is reachable from where the MCP server is running.