VOOZH about

URL: https://glama.ai/mcp/servers/integrations/influxdb

⇱ InfluxDB | Glama

  • Why this server?

    Supports the InfluxDB Line Protocol for seamless ingestion and management of time-series data.

  • Why this server?

    Uses InfluxDB to store and serve normalized 1-minute bars of cross-exchange orderflow data aggregated from 20 cryptocurrency exchanges.

    A
    license
    B
    quality
    B
    maintenance
    Cross-exchange crypto orderflow for AI agents. 20 exchanges, 26 tokens, 9 tools — CVD, whale activity, funding/OI, 7-year OHLCV, on-chain address risk (EVM + Solana). Pay-per-call USDC via x402, no API key.
    Last updated
    9
    31
    MIT

  • Why this server?

    Exposes access to an InfluxDB instance using the InfluxDB OSS API v2, allowing for organization and bucket management, measurement data access, writing time-series data, and executing Flux queries against the database.

    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that provides Claude with access to InfluxDB time-series database instances, enabling data writing, querying, and management of organizations and buckets through natural language.
    Last updated
    4
    3,799
    41
    MIT

  • Why this server?

    Supports writing data using InfluxDB Line Protocol format to GigAPI's timeseries database, enabling seamless data ingestion from InfluxDB-compatible sources.

    A
    license
    C
    quality
    C
    maintenance
    An MCP server that provides seamless integration with Claude Desktop for querying and managing timeseries data in GigAPI Timeseries Lake.
    Last updated
    7
    6
    Apache 2.0

  • Why this server?

    Connects to InfluxDB (v1 or v2) to discover, list, and analyze metrics from the sol_metrics database containing Solana blockchain data

    F
    license
    B
    quality
    D
    maintenance
    Analyzes Solana blockchain metrics from InfluxDB and generates categorized Grafana dashboards for monitoring consensus, network, banking, accounts, RPC, performance, and MEV metrics.
    Last updated
    4
    2

  • Why this server?

    Provides version compatibility checks and comparisons for InfluxDB, aiding in tool selection within a stack.

  • Why this server?

    Provides aggregation-first, bounded tools for querying time-series data from InfluxDB v2 using Flux, with tools for measurements, tags, fields, aggregate queries, top_n, count_events, latest, and a guarded raw-Flux escape hatch.

    A
    license
    -
    quality
    C
    maintenance
    A selective, aggregation-first MCP server for InfluxDB v2 that bounds output and pushes reduction to the database, avoiding context flooding from raw time-series data.
    Last updated
    MIT

  • Why this server?

    Provides tools for interacting with InfluxDB v3 (Core/Enterprise/Cloud Dedicated), including database management, querying with SQL, writing data using line protocol, managing measurements and schemas, and token administration.

    A
    license
    -
    quality
    D
    maintenance
    Enables interaction with InfluxDB v3 (Core/Enterprise/Cloud Dedicated) through MCP clients. Supports database management, data querying and writing, schema inspection, and token administration operations.
    Last updated
    3,799
    MIT

  • Why this server?

    Retrieves past messages and sensor data from InfluxDB as an alternative to Rosbag2 for ROS2 data storage and analysis.

    A
    license
    -
    quality
    D
    maintenance
    Enables AI tools to interact with ROS2 robotics systems through natural language commands. Supports topic publishing/subscribing, service calls, message analysis, and auto-discovery of ROS2 interfaces for debugging and controlling robots.
    Last updated
    Mozilla Public 2.0