How do I install Spoor?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Spoor need an API key?

The publisher lists these environment variables: SPOOR_METRICS_TYPE, SPOOR_LOGS_TYPE, SPOOR_TRACES_TYPE, SPOOR_METRICS_URL, SPOOR_LOGS_URL, SPOOR_TRACES_URL, SPOOR_METRICS_TOKEN, SPOOR_LOGS_TOKEN, SPOOR_TRACES_TOKEN, NEW_RELIC_ACCOUNT_ID, NEW_RELIC_API_KEY.

When was Spoor last checked?

Last checked 2026-11-09. What changed across metrics, logs and traces, and where it started (Grafana, Victoria, New Relic).

Spoor MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

docker run -i --rm ghcr.io/asinha07/spoor:0.3.1

Credentials from the publisher

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

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1SPOOR_METRICS_TYPE=<value> SPOOR_LOGS_TYPE=<value> SPOOR_TRACES_TYPE=<value> SPOOR_METRICS_URL=<value> SPOOR_LOGS_URL=<value> SPOOR_TRACES_URL=<value> SPOOR_METRICS_TOKEN=<secret> SPOOR_LOGS_TOKEN=<secret> SPOOR_TRACES_TOKEN=<secret> NEW_RELIC_ACCOUNT_ID=<value> NEW_RELIC_API_KEY=<secret> claude mcp add io.github.asinha07-spoor -- docker run -i --rm ghcr.io/asinha07/spoor:0.3.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.asinha07-spoor": {4      "command": "docker",5      "args": [6        "run",7        "-i",8        "--rm",9        "ghcr.io/asinha07/spoor:0.3.1"10      ],11      "env": {12        "SPOOR_METRICS_TYPE": "<value>",13        "SPOOR_LOGS_TYPE": "<value>",14        "SPOOR_TRACES_TYPE": "<value>",15        "SPOOR_METRICS_URL": "<value>",16        "SPOOR_LOGS_URL": "<value>",17        "SPOOR_TRACES_URL": "<value>",18        "SPOOR_METRICS_TOKEN": "<secret>",19        "SPOOR_LOGS_TOKEN": "<secret>",20        "SPOOR_TRACES_TOKEN": "<secret>",21        "NEW_RELIC_ACCOUNT_ID": "<value>",22        "NEW_RELIC_API_KEY": "<secret>"23      }24    }25  }26}

claude_desktop_config.json

Local · ociPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Spoor

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Spoor?

Does Spoor need an API key?

What transport does Spoor use?

When was Spoor last checked?

Documentation