OpenTelemetry Collector MCP Server

What is OpenTelemetry Collector MCP Server?

An MCP server that enables dynamic configuration of OpenTelemetry Collectors through tools and resources. It is designed for developers and operators who need to manage receiver, processor, and exporter components programmatically.

How to use OpenTelemetry Collector MCP Server?

Configure your MCP client by adding an entry to mcp.json with the server URL (e.g., http://localhost:3001/sse). Then use the provided tools to update component information and access resource URIs for receivers, processors, exporters, and component schemas.

Key features of OpenTelemetry Collector MCP Server

• Dynamic OpenTelemetry Collector configuration via MCP tools
• Component management for receivers, processors, and exporters
• Update Resources tool to refresh component data from GitHub
• Browse available components through receiver, processor, and exporter resources
• Retrieve configuration schemas for any supported component

Use cases of OpenTelemetry Collector MCP Server

• Automatically update local component catalogs from the OpenTelemetry GitHub repository
• Programmatically add, remove, or configure receivers, processors, and exporters in a collector
• Explore available components and their schemas to build valid configuration files
• Integrate OpenTelemetry Collector management into larger MCP‑based workflows

FAQ from OpenTelemetry Collector MCP Server

What does the OpenTelemetry Collector MCP Server do?

It provides tools and resources to dynamically configure an OpenTelemetry Collector, manage its components, and update component metadata from GitHub.

How do I configure it for use?

Add the server URL (http://localhost:3001/sse) under mcpServers in your MCP client’s mcp.json file.

What tools does it provide?

The server offers an Update Resources tool that refreshes local files with the latest component information from GitHub, returning statistics about updated receivers, processors, and exporters.

What resources are available?

Resources include receivers://receivers, processors://processors, and exporters://exporters for listing components, plus component://{type}/{name} for retrieving schemas of specific components.

What license is it under?

The server is licensed under the GPL-3.0 License, granting rights to use, modify, and distribute the software under that license’s terms.