edgedelta-mcp-server

Purpose

Edge Delta MCP Server is a server based on the Model Context Protocol (MCP), designed to provide seamless integration with the Edge Delta API, enabling developers and tools to achieve advanced automation and interaction capabilities. It is mainly used to extract and analyze observability data from Edge Delta, and supports building AI-driven tools and applications that interact with the Edge Delta platform.

Key Capabilities

1. Pipeline Configuration Tools: The server exposes tools for inspecting and changing Edge Delta pipelines. Write operations follow a safe loop: validate → save → deploy, and support rollback. A typical editing flow is:get_pipeline_config → edit YAML → validate_pipeline_config → save_pipeline_config → get_pipeline_history → deploy_pipeline(using revert_pipeline to roll back).
2. Live Capture Tools: Validating that a configuration is valid is not equivalent to confirming that a change actually transformed the data. Live capture tools sample the real before-and-after data of pipeline nodes on a running agent, so that the agent can verify whether the transformation took effect. Capture flow:start_pipeline_capture → get_pipeline_capture_status(poll until the agent reports success) → get_pipeline_capture_results(compare the before-and-after data of each node to confirm the transformation).
3. Processor Dry Run (Test) Tools: Develop and validate processors offline against sample logs—no save, no deploy, no live traffic. This is the offline complement to live capture: capture proves what actually happened, dry run proves what will happen. Iterate until the output is correct, then add the statement/node to the pipeline, execute save_pipeline_config → deploy_pipeline, and use the capture tools to confirm on live data. For OTTL transformations use test_pipeline_ottl(its ExtractPatterns also covers regex field extraction); for non-OTTL node types (such as log-to-metric and log-to-pattern), use test_pipeline_node.

Usage

Prerequisites

• Docker Engine ≥ 20.10 installed and running.
• Docker Buildx plugin available:
  • macOS / Windows – included in Docker Desktop.
  • Debian / Ubuntu:sudo apt-get update && sudo apt-get install -y docker-buildx-plugin
  • Fedora / RHEL / CentOS：sudo dnf install -y docker-buildx-plugin or yum install …
  • Other distributions (manual fallback):

    mkdir -p ~/.docker/cli-plugins
    curl -sSL \
      https://github.com/docker/buildx/releases/latest/download/buildx-$(uname -s | tr '[:upper:]' '[:lower:]')-amd64 \
      -o ~/.docker/cli-plugins/docker-buildx
    chmod +x ~/.docker/cli-plugins/docker-buildx
    

• An Edge Delta API token with the required scopes (create it here).
• Your Edge Delta organization ID (find it here).

Build (container image) First-time setup (create a multi-platform builder and start it): Build the image and load it into the local Docker daemon: ℹ️ The --load flag streams the image back to the local Docker engine so that you can directly use docker run mcp/edgedelta … to run it.

Use with Cursor

Applicable Scenarios

• Extract and analyze observability data from Edge Delta.
• Build AI-driven tools and applications that interact with the Edge Delta platform.
• Inspect, edit, validate, save, deploy, and roll back Edge Delta pipelines.
• Verify pipeline transformation effects through live capture.
• Develop and test processor logic offline to avoid affecting live traffic.

Limitations

• The Go API exported by this module is experimental and may change without notice. If you use it in production, please open an issue describing your use case so that the relevant interfaces can be stabilized.
• Prerequisites must be met (Docker, Buildx, API token, organization ID).
• License: MIT License. See LICENSE for details.
• Security policy: see the security policy in the repository.