Back to MCP Servers
🧩

Spoor MCP Server

API key required

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

To add Spoor to Claude, run the install command below. Restart Claude Code after adding it and its tools show up in your next conversation. It needs 11 environment variables, listed below.

DevTools

Install

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

Environment variables

SPOOR_METRICS_TYPESet in your MCP config
SPOOR_LOGS_TYPESet in your MCP config
SPOOR_TRACES_TYPESet in your MCP config
SPOOR_METRICS_URLSet in your MCP config
SPOOR_LOGS_URLSet in your MCP config
SPOOR_TRACES_URLSet in your MCP config
SPOOR_METRICS_TOKENSet in your MCP config
SPOOR_LOGS_TOKENSet in your MCP config
SPOOR_TRACES_TOKENSet in your MCP config
NEW_RELIC_ACCOUNT_IDSet in your MCP config
NEW_RELIC_API_KEYSet in your MCP config

What this does

Spoor exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

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

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install Spoor?

The install section on this page carries the maker's install command for Spoor, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Spoor?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to Spoor as well.

Does Spoor need an API key?

Yes. Before it can run, set 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. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-asinha07-spoor)](https://clauderules.net/mcp/io-github-asinha07-spoor)
HTML
<a href="https://clauderules.net/mcp/io-github-asinha07-spoor" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-asinha07-spoor" alt="Listed on clauderules.net" /></a>