Use the InfluxDB 3 MCP server

InfluxDB provides two Model Context Protocol (MCP) servers for integrating with AI assistants:

• Manage your InfluxDB instance with the database MCP server
• Query documentation from your IDE

Manage your InfluxDB instance with the database MCP server

The InfluxDB database MCP server lets you interact with InfluxDB 3 Enterprise using natural language with large language model (LLM) agents. It enables database management, token handling, and SQL query generation in plain English—no coding required.

This section walks you through configuring your LLM agent to run and use the InfluxDB database MCP server to interact with your InfluxDB 3 Enterprise server

.

Prerequisites

• Node.js v18+ (if using npx to run the MCP server)
• Docker (if using Docker to run the MCP server)
• A running and reachable InfluxDB 3 Enterprise server

.

• A valid InfluxDB 3 Enterprise admin or resource token with appropriate resource-specific permissions

• (Optional) An LLM assistant like Claude Desktop, ChatGPT Desktop, etc.

Configure the database MCP server

Use environment variables to configure the InfluxDB 3 MCP server and connect it to your InfluxDB 3 Enterprise server

. Set the following environment variables when you start the MCP server:

Required InfluxDB connection variables

• INFLUX_DB_PRODUCT_TYPE: enterprise

• INFLUX_DB_INSTANCE_URL: Your InfluxDB 3 Enterprise URL–for example:

  http://localhost:8181

  If using Docker to run the InfluxDB MCP server and you want to manage an InfluxDB instance running on localhost, use the internal Docker network to connect to your local InfluxDB 3 Enterprise server–for example:

  http://host.docker.internal:8181/

• INFLUX_DB_TOKEN: Your InfluxDB 3 Enterprise admin token or resource token.

  If using a resource token, your LLM agent can only perform the operations allowed by the token permissions.

Configure your LLM agent to run the database MCP server

To run the MCP server, use either Node.js and npm or Docker. Some LLM agents, like Claude Desktop, start, run, and connect to the MCP server for you.

The following instructions show how to configure Claude Desktop to use the InfluxDB database MCP server.

{
  "mcpServers": {
    "influxdb": {
      "command": "node",
      "args": ["/
path/to
/influxdb3_mcp_server/build/index.js"],
      "env": {
        "INFLUX_DB_PRODUCT_TYPE": "enterprise",
        "INFLUX_DB_INSTANCE_URL": "http://localhost:8181
",
        "INFLUX_DB_TOKEN": "
AUTH_TOKEN
"
      }
    }
  }
}

{
  "mcpServers": {
      "influxdb": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--env",
        "INFLUX_DB_PRODUCT_TYPE",
        "--env",
        "INFLUX_DB_INSTANCE_URL",
        "--env",
        "INFLUX_DB_TOKEN",
        "influxdata/influxdb3-mcp-server"
      ],
      "env": {
        "INFLUX_DB_PRODUCT_TYPE": "enterprise",
        "INFLUX_DB_INSTANCE_URL": "http://localhost:8181
",
        "INFLUX_DB_TOKEN": "
AUTH_TOKEN
"
      }
    }
  }
}

{
  "mcpServers": {
      "influxdb": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--add-host=host.docker.internal:host-gateway",
        "--env",
        "INFLUX_DB_PRODUCT_TYPE",
        "--env",
        "INFLUX_DB_INSTANCE_URL",
        "--env",
        "INFLUX_DB_TOKEN",
        "influxdata/influxdb3-mcp-server"
      ],
      "env": {
        "INFLUX_DB_PRODUCT_TYPE": "enterprise",
        "INFLUX_DB_INSTANCE_URL": "http://host.docker.internal:8181",
        "INFLUX_DB_TOKEN": "
AUTH_TOKEN
"
      }
    }
  }
}

Supported features

Once connected, you can use your LLM agent to perform tasks on your InfluxDB 3 Enterprise server

, including:

• Create, update, and delete databases
• List tables and inspect schemas
• Create and manage tokens
• Query data without writing SQL or InfluxQL
• Check server health and connection status

Examples of supported prompts

“List all tables in the production database.”

“Create a read-only token for the metrics database.”

“Analyze last week’s sensor data for anomalies.”

“Create a new database called iot_sensors with a 30-day retention policy.”

“Show me the schema for the sensor_data table.”

Query documentation from your IDE

The InfluxDB documentation MCP server lets AI tools and agents search InfluxDB InfluxDB 3 Enterprise documentation directly from your development environment. Use it to find answers, code examples, and configuration details without leaving your IDE.

Why use the documentation MCP server?

When you connect the documentation MCP server to your AI coding assistant, the assistant can search InfluxDB and related tool documentation to answer your questions with accurate, up-to-date information. Instead of switching to a browser or guessing at syntax, you can ask questions in your IDE and get responses grounded in official documentation.

Common use cases:

• Get help writing queries, client library code, or CLI commands
• Look up configuration options and environment variables
• Find code examples for specific tasks
• Troubleshoot errors with documentation-backed answers

Install the documentation MCP server

The documentation MCP server is a hosted service—you don’t need to install or run anything locally. Add the server URL to your AI assistant’s MCP configuration.

MCP server URL:

https://influxdb-docs.mcp.kapa.ai

The server uses SSE (Server-Sent Events) transport.

Configure your AI assistant to use the documentation MCP server

The following instructions show how to configure popular AI assistants to use the InfluxDB documentation MCP server.

{
  "mcpServers": {
    "influxdb-docs": {
      "url": "https://influxdb-docs.mcp.kapa.ai"
    }
  }
}

{
  "mcpServers": {
    "influxdb-docs": {
      "url": "https://influxdb-docs.mcp.kapa.ai",
      "transport": "sse"
    }
  }
}

{
  "servers": {
    "influxdb-docs": {
      "type": "http",
      "url": "https://influxdb-docs.mcp.kapa.ai"
    }
  }
}

{
  "mcpServers": {
    "influxdb-docs": {
      "url": "https://influxdb-docs.mcp.kapa.ai",
      "transport": "streamableHttp"
    }
  }
}

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "influxdb-docs": {
      "type": "remote",
      "url": "https://influxdb-docs.mcp.kapa.ai",
      "enabled": true
    }
  }
}

Authentication and rate limits

When you connect to the documentation MCP server for the first time, a Google sign-in window opens to complete an OAuth/OpenID Connect login.

The hosted MCP server:

• Requests only the openid scope from Google
• Receives an ID token (JWT) containing a stable, opaque user ID
• Does not request email or profile scopes—your name, email address, and other personal data are not collected

The anonymous Google ID enforces per-user rate limits to prevent abuse:

• 40 requests per user per hour
• 200 requests per user per day

Search documentation with the MCP tool

The documentation MCP server exposes a semantic search tool:

search_influxdb_knowledge_sources

This tool lets AI agents perform semantic retrieval over InfluxDB documentation and related knowledge sources.

What the tool does:

• Searches all InfluxDB documentation for a given query
• Returns the most relevant chunks in descending order of relevance
• Each chunk is a self-contained snippet from a single documentation page

Response format:

Each result includes:

• source_url: URL of the original documentation page
• content: The chunk content in Markdown

Use the documentation MCP server

After you install the documentation MCP server, your AI assistant can search InfluxDB documentation to help you with tasks. Ask questions naturally—the assistant uses the MCP server to find relevant documentation and provide accurate answers.

Example prompts

“How do I write data to InfluxDB using Python?”

“What’s the syntax for a SQL query with a WHERE clause in InfluxDB?”

“Show me how to configure Telegraf to collect CPU metrics.”

“What environment variables does the InfluxDB CLI use?”

“How do I create a database token with read-only permissions?”