Scout Monitoring MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOUT_API_KEY | Yes | Your Scout API key (read-only key that can be created on the Settings page) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_scout_setup_instructionsA | Get step-by-step instructions to instrument Scout APM in a framework. |
| list_appsA | |
| get_app_metricsA | Get individual metric data for a specific application. |
| get_app_endpointsA | |
| get_app_jobsA | |
| get_job_metricsB | |
| get_app_job_tracesA | |
| get_endpoint_metricsB | |
| get_app_endpoint_tracesA | |
| get_app_traceB | |
| get_app_error_groupsC | |
| get_usageA | Get usage and billing data for the current billing period. Returns billing period dates, pricing style, APM transaction counts (with limit if applicable), node counts (for per-node pricing), error counts (if error monitoring is enabled), and log bytes used (if logs integration is enabled). |
| get_app_insightsA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_available_metrics | List all available metrics for the Scout APM API. |
| list_config_resources | List all available Scout APM configuration templates. Returns a dictionary mapping library/framework names to their resource URIs. Use this to discover what configuration guides are available before fetching a specific one with scoutapm://config-resources/{library_name}. |
TDQS
Scored across 13 tools
The tools are mostly distinct by resource type—apps, endpoints, jobs, traces, errors, insights—but the metric tools (get_app_metrics, get_endpoint_metrics, get_job_metrics) share a very similar shape and could be confused at a glance. The endpoint path vs endpoint ID difference between get_endpoint_metrics and get_app_endpoint_traces adds another minor selection trap.
Most tools follow a readable get_<resource>_<detail> pattern and are consistently snake_case. However, list_apps breaks the get_* convention, and the placement of app is inconsistent (get_endpoint_metrics vs get_app_endpoint_traces, get_job_metrics vs get_app_job_traces).
Thirteen tools is well-scoped for an APM monitoring server. Each tool covers a meaningful query surface—setup, apps, metrics, endpoints, jobs, traces, errors, insights, and usage—without padding or redundant duplicates.
The server covers the core APM read workflows: instrumentation setup, app discovery, endpoint and job metrics, traces, error groups, insights, and billing. Minor gaps exist, such as no direct app-wide trace listing and no separate per-error detail endpoint, but agents can likely work around these using endpoint-filtered traces or error groups.