Otelcol MCP

🚀 OpenTelemetry Collector MCP Server

An MCP server implementation for configuring the OpenTelemetry Collector.

🚀 Quick Start

This is a local MCP server implementation for OpenTelemetry configuration. You can use it as follows:

1. Clone the repository.
2. Build the project using the provided build script.
3. Configure your MCP client to use this local server implementation.

✨ Features

• Dynamic OpenTelemetry Configuration: Configure the OpenTelemetry Collector via MCP tools.
• Component Management: Add, remove, and configure receivers, processors, and exporters.

🛠️ Tools

• Update Resources
  • Update local resource files from GitHub with the latest component information.
  • No input parameters are required.
  • Return statistics of the updated components (receivers, processors, exporters).

📦 Resources

• Receivers (receivers://receivers)

  • List all available OpenTelemetry receivers.
  • Return receiver metadata, including name, description, and stability.

• Processors (processors://processors)

  • List all available OpenTelemetry processors.
  • Return processor metadata, including name, description, and stability.

• Exporters (exporters://exporters)

  • List all available OpenTelemetry exporters.
  • Return exporter metadata, including name, description, and stability.

• Component Schema (component://{type}/{name})

  • Get the configuration schema for a specific component.
  • Support listing all available schemas or getting the schema for a specific component.
  • Parameters:
    • type: Component type ("receiver", "processor", or "exporter").
    • name: Name of the specific component (optional).

📚 Configuration

Usage with MCP Client

Add the following content to your mcp.json:

{
    "mcpServers": {
      "otelcol": {
        "url": "http://localhost:3001/sse"
      }
    }
}

📄 License

This MCP server is released under the GPL-3.0 license. This means you are free to use, modify, and distribute the software, but you must comply with the terms and conditions of the GPL-3.0 license. For more details, please refer to the LICENSE file in the project repository.