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 |
Capabilities
Features and capabilities supported by this server
| 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 |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dburton-influxdata/telegraf-controller-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server