This repository contains code to locally run an MCP server that can access [Scout Monitoring](https://www.scoutapm.com) data via Scout's API. We
This repository contains code to locally run an MCP server that can access Scout Monitoring data via Scout's API. We provide a Docker image that can be pulled and run by your AI Assistant to access Scout. The scout mcp local mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Tools — The Scout MCP provides the following tools for accessing Scout APM data:Resources — The Scout MCP provides configuration templates as resources that your AI assistant can read and apply:Installation goes through your MCP client rather than a global install: point it at @scout_apm/wizard on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: SCOUT_API_KEY, MAX_MCP_OUTPUT_TOKENS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The Wizard is a great way to get started, but you can also set things up manually. You will need to have or create a Scout Monitoring account and obtain an API key. 1. Sign up 2. Install the Scout Agent in your application and send Scout data! - Ruby -
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Scout MCP Local's toolset — Tools, Resources — is a fair guide to whether it matches your workflow. It is maintained by scoutapp; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Tools | The Scout MCP provides the following tools for accessing Scout APM data: |
| Resources | The Scout MCP provides configuration templates as resources that your AI assistant can read and apply: |
{
"mcpServers": {
"scout-apm": {
"command": "docker",
"args": ["run", "--rm", "-i", "--env", "SCOUT_API_KEY", "scoutapp/scout-mcp-local"],
"env": { "SCOUT_API_KEY": "your_scout_api_key_here"}
}
}
}Configuration as documented by the project. Restart the client after saving.
The Wizard is a great way to get started, but you can also set things up manually. You will need to have or create a Scout Monitoring account and obtain an API key. 1. Sign up 2. Install the Scout Agent in your application and send Scout data! - Ruby -
| Variable | Description | Required |
|---|---|---|
| SCOUT_API_KEY | Credential the server authenticates with. | Yes |
| MAX_MCP_OUTPUT_TOKENS | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.