Skip to main content
Glama
influxdata

InfluxDB MCP Server

Official
by influxdata

Related Servers

Alternatives to InfluxDB MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      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.
      678 npm
      MIT
    • 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.
      4
      678 npm
      45
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      InfluxDB-v1-MCP is a powerful Model Context Protocol (MCP) interface specifically designed for InfluxDB v1.x, enabling AI assistants to intelligently manage and query time-series databases.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Apache Flink clusters via the SQL Gateway, allowing query execution, session management, and job control through MCP tools.
      8
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 27 tools

    Disambiguation2/5

    Several tools overlap significantly: query_sql and execute_query both execute SQL queries, list_tables and get_measurements both list tables, and describe_table and get_measurement_schema both describe schemas. This creates ambiguity for an agent trying to select the right tool.

    Naming Consistency3/5

    Most tools follow a verb_noun snake_case pattern (create_database, delete_database, list_databases), but there are inconsistencies: get_help and health_check are not verb_noun, regenerate_operator_token uses an unusual verb, and cloud_* tokens are prefixed differently from other token tools. Overall readable but mixed.

    Tool Count2/5

    With 27 tools, the server is over the typical threshold for a coherent set. Many tools could be consolidated (e.g., query_sql and execute_query, list_tables and get_measurements) to reduce redundancy without losing functionality.

    Completeness4/5

    The server covers core database lifecycle (create/update/delete/list), query and write operations, schema introspection, and comprehensive token management across Cloud and Core/Enterprise. Minor gaps exist (e.g., no direct tool to delete data from a measurement), but the essential workflows are well represented.

    Maintenance

    ActivityActive
    ResponsivenessSlow