edgedelta

The Edge Delta MCP Server provides a bridge to your Edge Delta APIs via the MCP (Model Context Protocol). It enables automated interactions with Edge Delta, allowing tools and AI workflows to query observability data, trigger actions, and integrate with Edge Delta services. With this MCP server, you can expose a stable interface for clients to discover and interact with Edge Delta resources, making it easier to build automated tooling, dashboards, and AI assistants that harness Edge Delta data.

To use the server, deploy it in a container (as shown in the installation example) and configure your MCP client to connect to the server through the provided container image. The server expects two environment variables for authentication and scoping: ED_API_TOKEN for your Edge Delta API token and ED_ORG_ID for your Edge Delta organization ID. Once running, MCP clients can request context data, perform actions, and subscribe to updates according to the MCP specification. Typical workflows include fetching observability data, analyzing trends, and feeding insights into automated routines or AI-powered assistants that operate against Edge Delta’s platform.

Prerequisites:

• Docker Engine 20.10 or newer
• Docker Buildx plugin (included with Docker Desktop on macOS/Windows or installed via your distribution)
• An Edge Delta API token with the required scope
• Your Edge Delta organization ID

Installation steps:

1. Ensure Docker is running and Docker Buildx is available

   • Check: docker version
   • Check Buildx: docker buildx version

2. Build the MCP server image (first-time setup)

   • Create and boot a multi-arch builder (one-time): docker buildx create --name edgedelta-builder --use docker buildx inspect --bootstrap

3. Build and load the image into the local Docker daemon

   • Build and load the image: docker buildx build --load -t mcp/edgedelta .
   • This prints out the image tag and ensures the image is available locally for docker run.

4. Run the MCP server via Docker (as described in the configuration)

   • Run with environment variables by passing them to the container run command: docker run -i --rm
     -e ED_ORG_ID
     -e ED_API_TOKEN
     "ghcr.io/edgedelta/edgedelta-mcp-server:latest"

5. Verify connectivity

   • Ensure the MCP client can discover and communicate with the edgedelta MCP server using the mcp_config provided.

Notes:

• If you prefer not to pass secrets via command line, use a secret management approach compatible with your deployment environment and reference them in the container run environment.
• The example uses the latest tag; pin to a specific version for production stability.

Tips and common considerations:

• Ensure ED_API_TOKEN has the necessary scope for the operations you plan to perform in Edge Delta.
• ED_ORG_ID must match your Edge Delta organization identifier.
• When running in CI/CD, consider securely injecting environment variables and avoiding hard-coded tokens.
• If you encounter connectivity issues, verify network access to Edge Delta and that the token is valid.
• The container image ghcr.io/edgedelta/edgedelta-mcp-server:latest is pulled at run-time; you can pin to a specific version tag to guarantee stability.
• Review MCP client documentation to understand available context types and actions exposed by the edgedelta MCP server.