InfluxDB 3 MCP Server – Time Series Database Access
The InfluxDB 3 MCP server is an official InfluxData Model Context Protocol server for working with InfluxDB 3 Core, Enterprise, Cloud Serverless, Cloud Dedicated, and Clustered deployments. It gives MCP-capable assistants database tools for SQL queries, line protocol writes, database inspection, health checks, and token or database management when the configured token allows those operations.
Overview
The InfluxDB 3 MCP server connects AI assistants to InfluxDB 3 through the Model Context Protocol. It is intended for teams that want natural-language access to time-series and event data stored in InfluxDB while keeping the actual database access controlled by InfluxDB URLs, product-type settings, and tokens.
What the MCP server enables
The server exposes database-focused tools for common InfluxDB workflows. Documented tools include loading optional database context, getting help, writing line protocol, creating, updating, deleting, and listing databases, running SQL queries, listing measurements, reading measurement schemas, and checking connection health. For Core and Enterprise deployments, it can also create, list, delete, and regenerate tokens. For Cloud Dedicated and Clustered deployments, the cloud token tools manage database tokens when the required cloud credentials are provided.
The server also provides resources such as influx-config, influx-status, influx-databases, and an optional context file, plus prompts for listing databases, checking health, and loading context.
When to use it
Use this MCP server when an assistant needs to inspect or operate on InfluxDB 3 data and metadata from an MCP client. Practical examples include asking an IDE assistant to generate and run a SQL query against a database, check whether an InfluxDB 3 instance is reachable, inspect measurement schemas before writing code, write sample line protocol, or create a database for a new application environment.
Connection and authentication
The documented local transport is stdio, started either from a built Node.js checkout or from Docker. This entry uses the official Docker-based stdio pattern from InfluxData documentation. Required environment variables depend on the InfluxDB product type. Core and Enterprise use INFLUX_DB_INSTANCE_URL, INFLUX_DB_TOKEN, and INFLUX_DB_PRODUCT_TYPE; Cloud Serverless uses the same variables with cloud-serverless; Cloud Dedicated uses INFLUX_DB_CLUSTER_ID plus database and/or management tokens; Clustered deployments use an instance URL plus database and/or management tokens.
Key considerations
The MCP server can expose destructive and privileged operations if the configured token allows them, including deleting databases, creating full-permission admin tokens, deleting tokens, or regenerating an operator token. Use the least-privileged InfluxDB token that matches the intended workflow. Resource tokens limit the agent to the permissions granted by that token. Avoid passing admin or management tokens to general-purpose clients unless the workflow truly requires administrative database management.
Supported Transports
stdio
Command: docker
Args:
run--rm--interactive--envINFLUX_DB_PRODUCT_TYPE--envINFLUX_DB_INSTANCE_URL--envINFLUX_DB_TOKENinfluxdata/influxdb3-mcp-server
Frequently Asked Questions
- When should an AI agent use the InfluxDB 3 MCP server?
- Use it when an MCP-capable assistant needs controlled access to InfluxDB 3 time-series data or instance metadata, such as querying event data, inspecting measurements, checking database health, writing line protocol, or managing databases from a natural-language workflow.
- What does this MCP server add to an AI agent's capabilities?
- It gives the agent live InfluxDB 3 tools rather than relying on static model knowledge. The documented tools include SQL query execution, line protocol writes, database creation and updates, measurement and schema inspection, token operations for supported product types, and health checks.
- What can the AI agent access or manage through this server?
- Depending on the configured product type and token permissions, the agent can access databases, measurements, schemas, configuration and health resources, and optional context files. Administrative operations such as token creation, token deletion, database deletion, and operator-token regeneration require credentials with the matching permissions.
- How is authentication configured for this MCP server?
- Authentication is configured with InfluxDB environment variables. Core, Enterprise, and Cloud Serverless configurations use an instance URL, an InfluxDB token, and an `INFLUX_DB_PRODUCT_TYPE` value. Cloud Dedicated and Clustered deployments may also require cluster, account, database-token, and management-token variables depending on which operations are needed.
- Which transport should be used for this MCP server?
- Use the stdio transport for MCP clients that launch a local server process. InfluxData documents both Node.js and Docker startup patterns; this YAML uses Docker with the official `influxdata/influxdb3-mcp-server` image and passes credentials through environment variables.