Scout MCP Local

MCPAI代理

提供方 未标注

AI代理 HTTP · 远程 OAuth 授权 社区 / 第三方
查看接入方式

全面解析Scout MCP LocalMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Scout MCP Local能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Scout MCP Local 属于AI代理类 MCP 服务器,HTTP · 远程,OAuth 授权,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
npx 运行:

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Scout MCP Local当前 未标注 HTTP · 远程 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.0 KB
来自项目仓库与上游目录的原文,未做删改

Scout Monitoring MCP

<hr

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 Monitoring data.

This puts Scout Monitoring's performance and error data directly in the hands of your AI Assistant.
For Rails, Django, FastAPI, Laravel and more. Use it to get traces and errors with line-of-code information
that the AI can use to target fixes right in your editor and codebase. N+1 queries, slow endpoints,
slow queries, memory bloat, throughput issues - all your favorite performance problems surfaced
and explained right where you are working.

If this makes your life a tiny bit better, why not :star: it?!

Setup Wizard

The simplest way to configure and start using the Scout MCP is with our interactive setup wizard.
It handles all the prereqs and installation steps for you.

Run via npx:```bash
npx @scout_apm/wizard


Build and run from source:```bash
cd ./wizard
npm install
npm run build
node dist/wizard.js

The wizard will guide you through:
- Selecting your AI coding platform (Cursor, Claude Code, Claude Desktop)
- Entering your Scout API key
- Automatically configuring the MCP server settings

Supported Platforms

The wizard currently supports setup for:
- Cursor - Automatically configures MCP settings
- Claude Code (CLI) - Provides the correct command to run
- Claude Desktop - Updates the configuration file for Windows/Mac

For all others, it will output JSON that you can copy/paste into your AI Assistant's MCP configuration.

Prerequisites

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
    • Python
    • PHP
    • If you are trying this out locally, make sure monitor: true, errors_enabled: true
      are set in your config for the best experience
  3. Visit settings to get or create an API key
    • This is not your "Agent Key"; it's the "API Key" that can be created on the
      Settings page
    • This is a read-only key that can only access data in your account
  4. Install Docker. Instructions below assume you can start a Docker container

The MCP server will not currently start without an API key set, either in the
environment or by a command-line argument on startup.

Installation

We recommend using the provided Docker image to run the MCP server.
It is intended to be started by your AI Assistant and configured with your Scout API
key. Many local clients allow specifying a command to run the MCP server in some
location. A few examples are provided below.

The Docker image is available on Docker Hub.

Of course, you can always clone this repo and run the MCP server directly; uv or other
environment management tools are recommended.

Configure a local Client (e.g. Claude/Cursor/VS Code Copilot)

If you would like to configure the MCP manually, this usually just means supplying a command to run the MCP server with your API key in the environment
to your AI Assistant's config. Here is the shape of the JSON (the top-level key varies):```json
{
"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"}
}
}
}


 Claude Code```sh
claude mcp add scoutmcp -e SCOUT_API_KEY=your_scout_api_key_here -- docker run --rm -i -e SCOUT_API_KEY scoutapp/scout-mcp-local

Cursor

MAKE SURE to update the SCOUT_API_KEY value to your actual api key in
Arguments in the Cursor Settings > MCP

VS Code Copilot

  • VS Code Copilot docs
    • We recommend the "Add an MCP server to your workspace" option

Claude Desktop

Add the following to your claude config file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: `%APPDATA%/Claude/claude_desktop_config.json````json
{
"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"}
}
}
}


## Using the Scout Monitoring MCP

Scout&#x27;s MCP is intended to put error and performance data directly in the... hands? of your AI Assistant.
Use it to get traces and errors with line-of-code information that the AI can use to target
fixes right in your editor.

Most assistants will show you both raw tool calls and perform analysis. Desktop assistants
can readily create custom JS applications to explore whatever data you desire.
Assistants integrated into code editors can use trace data and error backtraces to make
fixes right in your codebase.

Combine Scout&#x27;s MCP with your AI Assistant&#x27;s other tools to:

- Create rich GitHub/GitLab issues based on errors and performance data
- Make JIRA fun - have your AI Assistant create tickets with all the details
- Generate PRs that fix specific errors and performance problems

### Tools

The Scout MCP provides the following tools for accessing Scout APM data:

- **`list_apps`** - List available Scout APM applications, with optional filtering by last active date
- **`get_app_metrics`** - Get individual metric data (response_time, throughput, etc.) for a specific application
- **`get_app_endpoints`** - Get all endpoints for an application with aggregated performance metrics
- **`get_endpoint_metrics`** - Get timeseries metrics for a specific endpoint in an application
- **`get_app_endpoint_traces`** - Get recent traces for an app filtered to a specific endpoint
- **`get_app_trace`** - Get an individual trace with all spans and detailed execution information
- **`get_app_error_groups`** - Get recent error groups for an app, optionally filtered by endpoint
- **`get_app_insights`** - Get performance insights including N+1 queries, memory bloat, and slow queries

### Resources

The Scout MCP provides configuration templates as resources that your AI assistant can read and apply:

- **`scoutapm://config-resources/{framework}`** - Setup instructions for supported framework or library (rails, django, flask, fastapi)
- **`scoutapm://config-resources/list`** - List all available configuration templates
- **`scoutapm://metrics`** - List of all available metrics for Scout APM

### Useful Prompts

#### Setup &amp; Configuration
- &quot;Help me set up Scout monitoring for my Rails application&quot;
- &quot;Create a Scout APM config file for my Django project with key ABC123&quot;

#### Performance &amp; Monitoring
- &quot;Summarize the available tools in the Scout Monitoring MCP.&quot;
- &quot;Find the slowest endpoints for app `my-app-name` in the last 7 days. Generate a table
  with the results including the average response time, throughput, and P95 response time.&quot;
- &quot;Show me the highest-frequency errors for app `Foo` in the last 24 hours. Get the
  latest error detail, examine the backtrace and suggest a fix.&quot;
- &quot;Get any recent n+1 insights for app `Bar`. Pull the specific trace by id and help me
  optimize it based on the backtrace data.&quot;

### Token Usage

We are currently more interested in expanding available information than strictly
controlling response size from our MCP tools. If your AI Assistant has a configurable
token limit (e.g. Claude Code `export MAX_MCP_OUTPUT_TOKENS=50000`), we recommend
setting it generously high, e.g. 50,000 tokens.

## Local Development

We use `uv` and `taskipy` to manage environments and run tasks for this project.

### Run with Inspector```bash
uv run task dev

Connect within inspector to add API key, set to STDIO transport

Build the Docker image```bash

docker build -t scout-mcp-local .


## Release

1. Branch and bump versions with `uv run python bump_versions.py`
1. Get that merged
1. Create a GitHub release with the new version (`gh release create v2025.11.3 --generate-notes --draft`)

Publishing the release pushes the `v*` tag, and CI publishes the Docker image, the PyPI package, and then the
MCP Registry entries:

- `server.json` → `com.scoutapm/scout-mcp-local` (this server; its version is bumped by `bump_versions.py`)
- `server.remote.json` → `com.scoutapm/scout-monitoring` (the hosted server at `https://scoutapm.com/mcp`). Bump its
  `version` by hand when you change its metadata; unchanged versions are skipped.

### MCP Registry key

The registry verifies we own the `com.scoutapm/*` namespace through a DNS TXT record at the `scoutapm.com` apex
holding an Ed25519 public key. CI signs in with the matching private key from the `MCP_REGISTRY_PRIVATE_KEY`
repository secret. To rotate it:```bash
openssl genpkey -algorithm Ed25519 -out key.pem
# Public key for the TXT record: replace the existing v=MCPv1 record, don&#x27;t add a second one
echo &quot;v=MCPv1; k=ed25519; p=$(openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)&quot;
# Private key (hex) for the MCP_REGISTRY_PRIVATE_KEY secret
openssl pkey -in key.pem -noout -text | grep -A3 &quot;priv:&quot; | tail -n +2 | tr -d &#x27; :\n&#x27;

For the bots:

mcp-name: com.scoutapm/scout-mcp-local

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Scout MCP Local 怎么安装?

在客户端按下面的安装命令接入:npx 运行:。装完在客户端配置里引用同一个包或端点。

Scout MCP Local 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Scout MCP Local 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Scout MCP Local 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Scout MCP Local 能提供哪些能力?

资料显示能力标签包括 JavaScript、性能监控、OAuth认证。具体工具清单以官方文档为准。

Scout MCP Local 需要什么运行环境?

运行时为 Node.js;属于远程端点,不需要在本地装运行时。

Scout MCP Local 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。