mcpField
O
OpenTelemetry Collector MCP Server

OpenTelemetry Collector MCP Server

Remote
github.com/mottibecDeveloper Tools52Updated 65w ago
Repository

About OpenTelemetry Collector MCP Server

OpenTelemetry Collector MCP Server configures OpenTelemetry Collectors through MCP tools. It is aimed at users who manage receiver, processor and exporter settings, and is licensed under GPL-3.0.

Key features

  1. 01Configure Collectors through MCP tools
  2. 02Add, remove and configure components
  3. 03Update component information from GitHub
  4. 04List receivers, processors and exporters
  5. 05Retrieve configuration schemas for components

Use cases

  1. 01Writing or adjusting OpenTelemetry Collector configuration
  2. 02Checking available components and their stability
  3. 03Assisting Collector configuration from an MCP client

MCP support

This is an MCP server that exposes component lists and schemas as resources, such as receivers://, processors://, exporters:// and component://, and provides an Update Resources tool to MCP clients.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttp://localhost:3001/sse
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

OpenTelemetry Collector MCP Server

An MCP server implementation for configuring OpenTelemetry Collectors.

Features

  • Dynamic OpenTelemetry Configuration: Configure OpenTelemetry Collectors through MCP tools
  • Component Management: Add, remove, and configure receivers, processors, and exporters

Tools

  • Update Resources
    • Updates local resource files with the latest component information from GitHub
    • No input parameters required
    • Returns statistics about updated components (receivers, processors, exporters)

Resources

  • Receivers (receivers://receivers)

    • Lists all available OpenTelemetry receivers
    • Returns receiver metadata including name, description, and stability

  • Processors (processors://processors)

    • Lists all available OpenTelemetry processors
    • Returns processor metadata including name, description, and stability

  • Exporters (exporters://exporters)

    • Lists all available OpenTelemetry exporters
    • Returns exporter metadata including name, description, and stability

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

    • Retrieves configuration schema for specific components
    • Supports listing all available schemas or getting a specific component's schema
    • Parameters:
      • type: Component type ("receiver", "processor", or "exporter")
      • name: Name of the specific component (optional)

Configuration

Usage with mcp clients

Add this to your mcp.json:

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

Development

This is a local implementation of an MCP server for OpenTelemetry configuration. To use it:

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

License

This MCP server is licensed under the GPL-3.0 License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the GPL-3.0 License. For more details, please see the LICENSE file in the project repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.