InfluxDB MCP Server
OfficialRelated Servers
Alternatives to InfluxDB MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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 npmMIT
- AlicenseAqualityBmaintenanceA 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.4518 npm47MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interactions with InfluxDB's open-source time-series database API, allowing data querying, management, and operations through natural language.-
- AlicenseNot gradedqualityDmaintenanceInfluxDB-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
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Apache Flink clusters via the SQL Gateway, allowing query execution, session management, and job control through MCP tools.8Apache 2.0
- AlicenseCqualityDmaintenanceExposes Databricks REST APIs as MCP tools for managing and querying a Databricks workspace, including clusters, jobs, SQL, Unity Catalog, and more.100MIT
TDQS
Scored across 25 tools
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.
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.
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.
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.