list_monitored_servicesLABSCO SUMMARY
An SLO breach followed all the way down to the trace.
The tools line up with the way an on-call engineer actually moves: which services are breaching, what the SLO said it promised, then the sampled traces sitting underneath it.
What it is
An MCP server over AWS Application Signals. It reads the monitored service inventory, SLI and SLO status, CloudWatch metrics and X-Ray traces, so an investigation runs from which service is unhealthy to which spans are slow in one place.
What you get
- Every service Application Signals monitors, listed
- Health detail for one named service
- CloudWatch metrics queried for a monitored service
- SLI status and SLO compliance across all services
- The full configuration of a single SLO
- Sampled X-Ray traces for distributed tracing analysis
- Transaction spans searched in X-Ray trace data
Requirements
AWS credentials already configured, through aws configure or environment variables, plus the uv package manager. The account has to have Application Signals enabled or there is nothing to list.
Setup effort
Add the configuration to your client
USE CASES
01
Finding out which service broke its SLO overnight
Read SLI status across every service, then open the configuration of the SLO that failed to see what it was measuring.
02
Getting your bearings in an account you did not set up
List everything under monitoring, then pull health detail on the services you do not recognise.
03
Checking whether a deploy moved latency
Query the CloudWatch metrics for the service either side of the release.
04
Following a slow request down to individual spans
Pull sampled traces for the window, then search the transaction spans inside them for where the time went.
7 tools
Listed in project docs. Your client may show a different list.
get_service_detailget_service_metricslist_slisget_sloquery_sampled_tracessearch_transaction_spansBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- AWS_ACCESS_KEY_ID in your environment
- AWS_SECRET_ACCESS_KEY in your environment
INSTALLATION
Connect your client
MCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"appsignals": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mxiamxia/appsignals-mcp.git",
"mcp-server-appsignals"
]
}
}
}Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · TERMINAL
git clone https://github.com/mxiamxia/appsignals-mcp.git
cd appsignals-mcp
uv pip install -e .CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"appsignals": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_APPSIGNALS_MCP>",
"run",
"mcp-server-appsignals"
]
}
}
}<YOUR_PATH_TO_APPSIGNALS_MCP> is the full path of the appsignals-mcp folder that git clone created.
Amazon Q Developer
AMAZON Q DEVELOPER · JSON
{
"mcpServers": {
"appsignals": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mxiamxia/appsignals-mcp.git",
"mcp-server-appsignals"
],
"env": {
"AWS_ACCESS_KEY_ID": "<YOUR_AWS_ACCESS_KEY_ID>",
"AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>"
},
"timeout": 60000
}
}
}
