Telegraf Controller MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAF_CONTROLLER_URL | Yes | Base URL of Telegraf Controller API | http://localhost:8888 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_configsA | List all Telegraf configurations with metadata |
| get_configA | Get a Telegraf configuration in TOML format with optional parameter substitution |
| get_config_detailsB | Get detailed metadata about a Telegraf configuration (JSON format) |
| create_configB | Create a new Telegraf configuration |
| update_configB | Update an existing Telegraf configuration |
| delete_configB | Delete a Telegraf configuration |
| list_agentsA | List Telegraf agents, optionally filtered by status |
| get_agent_detailsB | Get detailed information about a specific Telegraf agent |
| get_agent_summaryA | Get a summary of all agents including status breakdown and health percentage |
| delete_agentB | Delete a Telegraf agent from the controller |
| list_reporting_rulesA | List all reporting rules that define agent health thresholds |
| get_reporting_ruleB | Get details of a specific reporting rule |
| create_reporting_ruleB | Create a new reporting rule to define when agents are considered unhealthy |
| update_reporting_ruleD | Update an existing reporting rule |
| delete_reporting_ruleA | Delete a reporting rule (agents using it will be reassigned to default rule) |
| health_checkA | Check the health status of the Telegraf Controller |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check-agent-health | Generate a comprehensive health check report for all Telegraf agents |
| troubleshoot-not-reporting | Diagnose why agents are not reporting and provide troubleshooting steps |
| create-config-from-template | Guide through creating a Telegraf configuration for a specific use case |
| deploy-config-to-agents | Provide instructions for deploying a configuration to Telegraf agents |
| optimize-reporting-rules | Analyze current reporting rules and suggest optimizations |
| agent-fleet-overview | Generate a comprehensive overview of the Telegraf agent fleet |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Telegraf Controller Status | Real-time controller and agent status including health summary |
| Telegraf Configurations | List of all Telegraf configurations with metadata |
| Telegraf Agents | List of all Telegraf agents with status information |
| Reporting Rules | Agent health reporting rules and thresholds |
TDQS
Scored across 16 tools
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.
All tools follow a consistent verb_noun pattern: list_, get_, create_, update_, delete_. Even health_check fits the pattern. No camelCase or mixed styles.
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.
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.