Skip to main content
Glama
InfluxDB MCP Server

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.
      518 npm
      MIT
    • A
      license
      A
      quality
      B
      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
      518 npm
      47
      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

    B3.4/5.0

    Scored across 25 tools

    Disambiguation2/5

    Several tool pairs overlap directly: list_tables vs get_measurements both list tables/measurements, describe_table vs get_measurement_schema both return schema, and query_sql vs execute_query both execute SQL with execute_query merely deprecated. The split between cloud_* database token tools and admin-token tools is also easy to confuse, even though descriptions sometimes clarify product scope.

    Naming Consistency3/5

    Most names are snake_case verb_noun, but conventions are inconsistent: some tools carry a cloud_ prefix while equivalent admin-token tools do not, and same-purpose operations use different verbs (list_tables vs get_measurements, describe_table vs get_measurement_schema). health_check also breaks the verb_noun pattern, though names remain readable.

    Tool Count3/5

    25 tools is on the heavy borderline for an InfluxDB server, and several slots are occupied by deprecated or duplicate operations (execute_query, get_measurements, get_measurement_schema). Multi-version and product-specific token management explains part of the count, but the surface feels inflated rather than tightly scoped.

    Completeness4/5

    Core database lifecycle CRUD, SQL/InfluxQL querying, schema discovery, line-protocol writes, health checks, and token management for both cloud and Core/Enterprise are present. Remaining gaps are minor—notably no explicit data/table deletion operation and limited non-database resource coverage—but agents can generally work around them.

    Maintenance

    ActivityActive
    ResponsivenessLimited data