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.678 npmMIT
- AlicenseAqualityDmaintenanceA 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.4678 npm45MIT
- 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 27 tools
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.
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.
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.
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.