Skip to main content
Glama
dburton-influxdata

Telegraf Controller MCP Server

by dburton-influxdata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Telegraf Controller MCP Server

No user-submitted related servers found.

    Related Servers

    • NetPulse

      hind77
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.
      6
      MIT

    • defined-mcp

      geoffbelknap
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to manage Defined Networking / Managed Nebula infrastructure, supporting tasks like network topology design, host provisioning, and security auditing through natural language.
      4
      MIT

    • linux-ssh-mcp

      JINDEZHIDIYE
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.
      MIT

    • Metabase MCP Plus

      schachan
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      MIT

    • ha-mcp

      osrd-gh
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.
      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

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Tools are largely distinct, but get_config and get_config_details could be confused without reading descriptions carefully. get_agent_details and get_agent_summary are clearly differentiated by scope.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: list_, get_, create_, update_, delete_. Even health_check fits the pattern. No camelCase or mixed styles.

    Tool Count4/5

    16 tools is on the higher side but appropriate for managing three distinct resources (configs, agents, reporting rules). Each tool serves a clear purpose and the count is not excessive.

    Completeness4/5

    Configs and reporting rules have full CRUD coverage. Agents lack create/update operations, but this may be intentional since agents are likely auto-discovered. No major dead ends for the core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources