Skip to main content
Glama
dmayan-ss

mcflux

by dmayan-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcflux

No user-submitted related servers found.

    Related Servers

    • InfluxDB MCP Server

      idoru
      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
      243 npm
      44
      MIT

    • MariaDB MCP Server

      abel9851
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server implementation that enables Claude to execute read-only queries against MariaDB databases and explore database schemas through natural language.
      20
      MIT

    • influx-mcp

      nickcheban
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for InfluxDB 2.x, tuned for Home Assistant long-term storage, enabling reading sensor history, finding anomalies, and running Flux queries.
      1
      MIT

    • SQL Server MCP

      millelog
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for SQL Server database introspection that enables Claude to explore and query databases via tools like listing objects and executing SELECT queries.
      20
      1
      MIT

    • clickhouse-mcp

      jvanvalkenhoef
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for ClickHouse that enables AI agents to discover schema, sample data, and run read-only SQL queries to investigate observability data like logs, metrics, and traces.
      6
      11 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct purpose: ping for connectivity, list_* tools for schema exploration (databases, measurements, tags, fields), and query for executing InfluxQL. No overlapping functionality.

    Naming Consistency4/5

    Most tools follow the verb_noun pattern (list_databases, list_measurements, etc.). 'ping' and 'query' are exceptions but are standard, recognizable verbs in this context, so naming remains predictable.

    Tool Count5/5

    Seven tools is well within the ideal range for a focused server. Each tool addresses a core aspect of read-only InfluxDB interaction without redundancy.

    Completeness5/5

    The toolset covers the full read-only lifecycle: connectivity, database listing, schema exploration (measurements, tags, fields), and querying. Any missing metadata can be obtained through the query tool with SHOW statements.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources