Home › Cloud & Monitoring › Spoor
Spoor
What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic).
Topics: Monitoring
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (oci)
docker run -i --rm -e SPOOR_METRICS_TOKEN=<YOUR_VALUE> -e SPOOR_LOGS_TOKEN=<YOUR_VALUE> -e SPOOR_TRACES_TOKEN=<YOUR_VALUE> -e NEW_RELIC_API_KEY=<YOUR_VALUE> ghcr.io/asinha07/spoor:0.3.1
Or add to your MCP client config:
{
"mcpServers": {
"spoor": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SPOOR_METRICS_TOKEN=<YOUR_VALUE>",
"-e",
"SPOOR_LOGS_TOKEN=<YOUR_VALUE>",
"-e",
"SPOOR_TRACES_TOKEN=<YOUR_VALUE>",
"-e",
"NEW_RELIC_API_KEY=<YOUR_VALUE>",
"ghcr.io/asinha07/spoor:0.3.1"
]
}
}
}
SPOOR_METRICS_TYPE— Backend for metrics: victoriametrics (default), prometheus or newrelicSPOOR_LOGS_TYPE— Backend for logs: victorialogs (default), loki or newrelicSPOOR_TRACES_TYPE— Backend for traces: victoriatraces (default), tempo or newrelicSPOOR_METRICS_URL— Metrics backend URL (VictoriaMetrics or Prometheus) as seen from the container, e.g. http://host.docker.internal:8428SPOOR_LOGS_URL— Logs backend URL (VictoriaLogs or Loki) as seen from the container, e.g. http://host.docker.internal:9428SPOOR_TRACES_URL— Traces backend URL (VictoriaTraces or Tempo) as seen from the container, e.g. http://host.docker.internal:10428SPOOR_METRICS_TOKENsecret — Bearer token for the metrics backend, if it requires oneSPOOR_LOGS_TOKENsecret — Bearer token for the logs backend, if it requires oneSPOOR_TRACES_TOKENsecret — Bearer token for the traces backend, if it requires oneNEW_RELIC_ACCOUNT_ID— New Relic account ID, for signals of type newrelicNEW_RELIC_API_KEYsecret — New Relic User API key (NRAK-...), for signals of type newrelic
This server takes extra arguments — see its repository.
Related servers
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Grafana
An MCP server giving access to Grafana dashboards, data and more.
Sentry
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
homebutler
Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.
mpeirone/zabbix-mcp-server
Zabbix integration for hosts, items, triggers, templates, problems, data and more.
initmax/zabbix-mcp-server
Self-hosted Zabbix integration with 237 tools, multi-server monitoring, problem investigation, graphs, capacity forecasts, PDF reports,…
Listed in punkpeye/awesome-mcp-servers (MIT)
Data from the Official MCP Registry