# Scout Monitoring (local)

A local MCP server that hands Scout APM data to your coding assistant: app metrics, endpoints, traces, errors, N+1 insights. You get performance fixes suggested right where you work.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 30
- Author: scoutapp
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/scoutapp/scout-mcp-local
- Updated: 2026-10-20
- HTML: https://affpapa.org/en/nevibecode/mcp/scout-monitoring-local

## What it does

The server pulls Scout Monitoring data through Scout's API and exposes it as MCP tools. Your assistant can read traces and errors with line-of-code details, then target fixes in the editor. Slow endpoints, N+1 queries, memory bloat, throughput problems — the usual suspects show up next to the code that causes them.

It ships as a Docker image, `scoutapp/scout-mcp-local`, meant to be started by the assistant itself. The tool set includes `list_apps`, `get_app_metrics`, `get_app_endpoints`, `get_endpoint_metrics`, and `get_app_endpoint_traces`. Editor-integrated assistants use traces and backtraces to edit code directly. Desktop assistants can build small JS apps to explore whatever data you need.

The server refuses to start without an API key: set `SCOUT_API_KEY` in the environment or pass it as a command-line argument. It is a read-only key created on Scout's settings page, not the Agent Key. Docker is required. For local trials, the README suggests `monitor: true` and `errors_enabled: true` in the agent config so data actually flows.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `SCOUT_API_KEY` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add scout-mcp-local -e SCOUT_API_KEY=<SCOUT_API_KEY> -- uvx scout-mcp-local
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from scout-mcp-local <command>

### Codex

**Platform CLI**
```bash
codex mcp add scout-monitoring-local --env SCOUT_API_KEY=<SCOUT_API_KEY> -- uvx scout-mcp-local
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from scout-mcp-local <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "scout-monitoring-local": {
            "command": "uvx",
            "args": [
                "scout-mcp-local"
            ],
            "env": {
                "SCOUT_API_KEY": "<SCOUT_API_KEY>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from scout-mcp-local <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "scout-monitoring-local": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "scout-mcp-local"
            ],
            "env": {
                "SCOUT_API_KEY": "<SCOUT_API_KEY>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from scout-mcp-local <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e SCOUT_API_KEY=<SCOUT_API_KEY> scout-monitoring-local uvx scout-mcp-local
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from scout-mcp-local <command>

## When to use it
- Spot N+1 queries from trace data
- Get an error backtrace with the exact code line
- Read response_time and throughput per app
- List all endpoints with aggregated performance numbers
- File a GitHub issue or Jira ticket from an error trace

## Example prompts
- List the Scout APM apps I have access to
- Check `my-app` for N+1 queries in the last 24 hours
- Pull metrics for the `/checkout` endpoint and tell me why it lags

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md