How edgedelta/edgedelta-mcp-server works
Project type and purpose
• This is a Go-based, containerized backend service (“monolith” in the sense that all business logic lives in one process) plus a companion CLI tool.
• It implements a Model Context Protocol (MCP) server that developers and tools (e.g. Cursor) can call, and it calls out to Edge Delta’s APIs.
File structure
• Top-level directories:
• cmd/mcp-server – the main server binary (incoming MCP requests).
• cmd/mcp-curl – a lightweight CLI for exercising the MCP server.
• pkg/core – all business logic: protocol handling, client wrapper for Edge Delta API, event/log management, anomaly detection, patterns, etc.
• .github/workflows & goreleaser config – CI/CD pipelines for linting, testing, Docker image build/publish.
• Dockerfile – containerizes the server.
• Scripts/license checks and contributing/docs are support artifacts.
README for additional insights
• The service is delivered as a Docker image, driven by environment variables (ED_API_TOKEN, ED_ORG_ID).
• Customers embed it into their “Cursor” config or run it standalone via “docker run”.
• It’s intended for data extraction and AI-powered tooling against Edge Delta.