SSyncDev

Spoor MCP Server

What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic).

Local serverstdio

What is the Spoor MCP Server?

Spoor is an MCP integration. What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic).

Packages and local setup

The published oci package is ghcr.io/asinha07/spoor:0.3.1. Its declared MCP transport is stdio.

The package declares SPOOR_METRICS_TYPE: Backend for metrics: victoriametrics (default), prometheus or newrelic; SPOOR_LOGS_TYPE: Backend for logs: victorialogs (default), loki or newrelic; SPOOR_TRACES_TYPE: Backend for traces: victoriatraces (default), tempo or newrelic; SPOOR_METRICS_URL: Metrics backend URL (VictoriaMetrics or Prometheus) as seen from the container, e.g. http://host.docker.internal:8428; SPOOR_LOGS_URL: Logs backend URL (VictoriaLogs or Loki) as seen from the container, e.g. http://host.docker.internal:9428; SPOOR_TRACES_URL: Traces backend URL (VictoriaTraces or Tempo) as seen from the container, e.g. http://host.docker.internal:10428; SPOOR_METRICS_TOKEN: Bearer token for the metrics backend, if it requires one; SPOOR_LOGS_TOKEN: Bearer token for the logs backend, if it requires one; SPOOR_TRACES_TOKEN: Bearer token for the traces backend, if it requires one; NEW_RELIC_ACCOUNT_ID: New Relic account ID, for signals of type newrelic; NEW_RELIC_API_KEY: New Relic User API key (NRAK-...), for signals of type newrelic.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.3.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related monitoring & observability MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
SPOOR_METRICS_TYPEBackend for metrics: victoriametrics (default), prometheus or newrelicCheck documentation
SPOOR_LOGS_TYPEBackend for logs: victorialogs (default), loki or newrelicCheck documentation
SPOOR_TRACES_TYPEBackend for traces: victoriatraces (default), tempo or newrelicCheck documentation
SPOOR_METRICS_URLMetrics backend URL (VictoriaMetrics or Prometheus) as seen from the container, e.g. http://host.docker.internal:8428Check documentation
SPOOR_LOGS_URLLogs backend URL (VictoriaLogs or Loki) as seen from the container, e.g. http://host.docker.internal:9428Check documentation
SPOOR_TRACES_URLTraces backend URL (VictoriaTraces or Tempo) as seen from the container, e.g. http://host.docker.internal:10428Check documentation
SPOOR_METRICS_TOKENBearer token for the metrics backend, if it requires oneCheck documentation
SPOOR_LOGS_TOKENBearer token for the logs backend, if it requires oneCheck documentation
SPOOR_TRACES_TOKENBearer token for the traces backend, if it requires oneCheck documentation
NEW_RELIC_ACCOUNT_IDNew Relic account ID, for signals of type newrelicCheck documentation
NEW_RELIC_API_KEYNew Relic User API key (NRAK-...), for signals of type newrelicCheck documentation