OpenTelemetry

You can configure and manage OpenTelemetry Collectors through an MCP server that exposes component data and runtime configuration. This server lets you update local component information, list available receivers, processors, and exporters, and fetch schemas to tailor your OpenTelemetry setup without editing files directly.

How to use

To configure OpenTelemetry Collectors via MCP, you connect your MCP client to the server and use the provided tools to update resources, inspect available components, and retrieve component schemas. You can dynamically adjust receivers, processors, and exporters and apply these changes to your local OpenTelemetry Collector configuration.

Key actions you can perform:

How to install

Prerequisites: you need a Git client to clone the project and a runtime environment capable of building and running the MCP server. The following steps assume a JavaScript/TypeScript-oriented build flow commonly used for MCP servers.

1. Clone the repository using the standard Git command.

2. Change into the project directory.

3. Install dependencies using the project’s package manager.

4. Build the project using the provided build scripts.

5. Run the MCP server locally and point your MCP client to the local endpoint.

Configuration and usage notes

The server exposes an HTTP endpoint you can use to connect an MCP client. You can reference the example configuration below to wire the client to the local server. This is the primary way to connect and test the MCP server locally.

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

Available tools

Update Resources

Updates local resource files with the latest component information from GitHub and returns statistics about updated components (receivers, processors, exporters)