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. Always use this tool first when asked to setup/instrument/configure Scout APM in an application. This provides official, tested configuration instructions that should be followed exactly. Supported frameworks:
Args: framework: The framework or library name (e.g., "fastapi", "django", "celery") Returns: Complete setup instructions including installation, configuration, and examples. |
| list_appsA | List available Scout APM applications. Provide an optional Args: active_since (str): ISO 8601 datetime string to filter apps active since that time. |
| get_app_metricsB | Get individual metric data for a specific application. Args: app_id (int): The ID of the Scout APM application. metric (str): The metric to retrieve (e.g., "response_time", "throughput"). from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_app_endpointsA | Get all endpoints for a specific application. Also gets aggregated performance metrics withing the window of "from_" to "to". Useful for identifying high throughput, high latency or high error rate endpoints accross the application with a single call. These endpoints can be used in other tools to fetch endpoint-specific metrics, traces or errors. Args: app_id (int): The ID of the Scout APM application. from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_app_jobsA | Get all background jobs for a specific application. Also gets aggregated performance metrics within the window of "from_" to "to". Useful for identifying high throughput, high latency or high error rate jobs across the application with a single call. Each job includes: full_name, name, queue, job_id, throughput, execution_time, time_consumed, latency. Args: app_id (int): The ID of the Scout APM application. from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_job_metricsA | Get a single timeseries metric for a specific background job in an application. Valid job metrics: throughput, execution_time, latency, errors, allocations. Args: app_id (int): The ID of the Scout APM application. job_id (str): The Base64-encoded job ID. metric (str): The metric to retrieve (e.g., "execution_time", "throughput"). from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_app_job_tracesB | Get recent traces for an app filtered to a specific background job. Each trace includes: id, time, duration, name, queue, metric_name, context. Args: app_id (int): The ID of the Scout APM application. job_id (str): The Base64-encoded job ID. from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_endpoint_metricsB | Get a single timeseries metric for a specific endpoint in an application. Args: app_id (int): The ID of the Scout APM application. endpoint (str): The endpoint path (e.g., "/users", "/orders"). metric (str): The metric to retrieve (e.g., "response_time", "throughput"). from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_app_endpoint_tracesC | Get recent traces for an app filtered to a specific endpoint. Args: app_id (int): The ID of the Scout APM application. endpoint_id (str): The ID of the endpoint to filter traces. from_ (str): The start datetime in ISO 8601 format. to (str): The end datetime in ISO 8601 format. |
| get_app_traceA | Get an individual trace with all spans. Args: app_id (int): The ID of the Scout APM application. trace_id (int): The ID of the trace to retrieve. |
| get_app_error_groupsC | Get recent error_groups for an app, optionally filtered to a specific endpoint or group. Args: app_id (int): The ID of the Scout APM application. endpoint_id (str | None): The ID of the endpoint to filter errors. If None, fetches all errors for the app. error_group_id (str | None): The ID of the error group to filter errors. |
| get_app_anomaly_eventsA | List anomaly events for a Scout APM application within a timeframe. Anomaly events flag statistically significant deviations in a metric (e.g. response time spike, throughput drop) detected against a learned baseline. Args: app_id: The ID of the Scout APM application. from_: Start datetime in ISO 8601 format. to: End datetime in ISO 8601 format. state: Filter by state - "open", "closed", or "all". metric: Filter by metric (e.g. response_time, throughput, error_rate). endpoint: Filter by endpoint (controller path). |
| get_app_anomaly_eventB | Get a single anomaly event by ID, with smart_monitor and deploy context. |
| 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 | Get or generate all insights for an application (cached for 5 minutes). Returns performance insights including N+1 queries, memory bloat, and slow queries. Each insight type includes count, new_count, and items array with specific details. If insight_type is provided, only that type will be returned. Args: app_id (int): The ID of the Scout APM application. insight_type: (str | None): Type of insight to filter (n_plus_one, memory_bloat, slow_query) If None (the default), all types will be returned. limit (int | None): Maximum number of items per insight type (default: 20). |
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 15 tools
The tools mostly target distinct resources and actions, and descriptions clarify scope. There is some potential confusion among the metric/trace families (app, job, endpoint metrics; app trace vs job/endpoint traces), but the naming and parameter descriptions make them separable.
All tools use snake_case with a predictable verb_noun pattern, mostly get_* or list_*, and the singular/plural distinction is meaningful. The set is consistently readable and follows a clear convention throughout.
Fifteen tools is well-scoped for an APM monitoring server covering apps, metrics, traces, jobs, endpoints, errors, anomalies, insights, usage, and setup. Each tool appears to earn its place without excessive surface area.
The surface covers the major monitoring workflows: discovering apps, inspecting metrics and traces across apps/jobs/endpoints, error groups, anomalies, insights, usage, and setup instructions. Minor gaps remain around drilling into individual error group details or deeper error diagnostics, but most workflows are workable.