A Model Context Protocol (MCP) server for InfluxDB that enables Claude and other AI assistants to work with time-series data
Connect Influxdb to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for InfluxDB that enables Claude and other AI assistants to work with time-series data. The influxdb mcp server is what makes that connection.
A Model Context Protocol (MCP) server that exposes access to an InfluxDB v2 instance using the InfluxDB OSS API v2. Mostly built with Claude Code.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Parameters — org, bucket, data, precision (optional)Configuration is passed through the environment: INFLUXDB_TOKEN, INFLUXDB_URL, INFLUXDB_ORG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Influxdb's toolset — Parameters — is a fair guide to whether it matches your workflow. It is maintained by idoru; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Parameters | org, bucket, data, precision (optional) |
### If installed locally
```json
{
"mcpServers": {
"influxdb": {
"command": "node",
"args": ["/path/to/influxdb-mcp-server/src/index.js"],
"env": {
"INFLUXDB_TOKEN": "your_token",
"INFLUXDB_URL": "http://localhost:8086",
"INFLUXDB_ORG": "your_org"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| INFLUXDB_TOKEN | Credential the server authenticates with. | Yes |
| INFLUXDB_URL | Endpoint or connection string the server talks to. | Yes |
| INFLUXDB_ORG | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.