Model Context Protocol (MCP) server that lets Claude or other AI assistants read/write/query an InfluxDB instance through the InfluxDB OSS v2 API.
https://github.com/idoru/influxdb-mcp-serverStop context-switching between Claude and your InfluxDB dashboard. This MCP server puts your time-series data directly into your AI conversation, letting you query, analyze, and write data without leaving your chat.
Working with InfluxDB usually means jumping between multiple tools: Claude for analysis insights, the InfluxDB UI for queries, your terminal for data writes, and documentation for Flux syntax. This server eliminates that friction by making your InfluxDB instance directly accessible to Claude.
Ask Claude to "show me CPU usage spikes from the past hour" and get real data back. Request trend analysis on sensor readings, write new measurements, or even create buckets—all through natural conversation.
Direct Database Access: Claude can read your organizations, buckets, and measurements as resources, giving it full context of your data structure.
Intelligent Querying: Built-in Flux query examples and line protocol guides mean Claude knows how to construct proper queries for your specific use case.
Write Capabilities: Not just read-only—Claude can write time-series data, create buckets, and manage organizations based on your requests.
Zero Context Loss: Your database schema and recent query results stay in the conversation context, enabling follow-up analysis and iterative exploration.
IoT Data Analysis: "Claude, show me temperature anomalies from sensor_network bucket over the last 24 hours, then calculate the correlation with humidity readings."
System Monitoring: "Find all servers where memory usage exceeded 80% yesterday and write a summary report of the incidents."
Performance Debugging: "Query response times from the past week, identify the slowest endpoints, and suggest optimization areas based on the patterns."
Data Pipeline Validation: "Check if all expected metrics are being written to the production bucket and flag any missing measurements."
Install via npx (no global installation needed):
INFLUXDB_TOKEN=your_token npx influxdb-mcp-server
Add to your Claude Desktop config:
{
"mcpServers": {
"influxdb": {
"command": "npx",
"args": ["influxdb-mcp-server"],
"env": {
"INFLUXDB_TOKEN": "your_token",
"INFLUXDB_URL": "http://localhost:8086"
}
}
}
}
That's it. Claude now has direct access to your InfluxDB instance.
The server exposes your InfluxDB through three MCP primitives:
The modular architecture means you can extend functionality by adding handlers in the src/handlers/ directory. Each component handles a specific aspect of InfluxDB interaction, making the codebase easy to understand and modify.
This isn't a proof-of-concept—it includes comprehensive integration tests that spin up actual InfluxDB containers and validate all functionality. The code structure follows Node.js best practices with proper error handling, logging, and environment configuration.
You can run it locally for development, deploy it as a service, or use it directly through npx for immediate access. The Smithery integration means one-command installation for Claude Desktop users.
Your time-series data deserves better than manual query construction and context switching. Let Claude handle the heavy lifting while you focus on insights and decisions.