- Home
- MCP servers
- Appsignals
Appsignals
- typescript
1
GitHub Stars
typescript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"mxiamxia-appsignals-mcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mxiamxia/appsignals-mcp.git",
"mcp-server-appsignals"
],
"env": {
"AWS_ACCESS_KEY_ID": "<aws_access_key>",
"AWS_SECRET_ACCESS_KEY": "<aws_secret_access_key>"
}
}
}
}This MCP server provides tools to monitor, analyze, and troubleshoot AWS Application Signals services. It lets you track service health, monitor SLOs, query metrics, and investigate distributed traces, all accessible through an MCP client.
How to use
You interact with this MCP server from an MCP client to perform operations like listing monitored services, checking service health, retrieving metrics, and querying traces. Use the client to run the available tools in sequence or pick a single tool to answer a specific question about your AWS Application Signals setup. Practical patterns include monitoring service health across all services, validating SLO compliance at scale, and drilling into traces to pinpoint bottlenecks or failures.
How to install
Prerequisites you need before installing and running the MCP server are clearly defined so you can prepare your environment.
{
"mcpServers": {
"appsignals": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mxiamxia/appsignals-mcp.git",
"mcp-server-appsignals"
]
}
}
}
If you prefer a local installation approach, you can install dependencies and run the server using a directory path you specify. Then configure Claude Desktop to run the server from that directory.
{
"mcpServers": {
"appsignals": {
"command": "uv",
"args": [
"--directory",
"/path/to/appsignals-mcp",
"run",
"mcp-server-appsignals"
]
}
}
}
Amazon Q integration is supported similarly. You can configure the MCP entry with runtime environment variables for AWS credentials to enable AWS Q integration.
{
"mcpServers": {
"appsignals": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mxiamxia/appsignals-mcp.git",
"mcp-server-appsignals"
],
"env": {
"AWS_ACCESS_KEY_ID": "<aws_access_key>",
"AWS_SECRET_ACCESS_KEY": "<aws_secret_access_key>"
},
"timeout": 60000
}
}
}
Additional notes
Security and credentials: Keep AWS credentials and any other secrets in secure storage. Use environment variables only in trusted contexts and rotate keys regularly.
Troubleshooting: If the MCP server fails to start, verify that you have access to the GitHub repository, that the uv/uvx runtimes are installed, and that the directory paths used in the local installation method exist and contain the MCP server package.
Available tools
list_monitored_services
Lists all services monitored by AWS Application Signals.
get_service_detail
Retrieves detailed healthy data for a specific service.
get_service_metrics
Queries CloudWatch metrics for the monitored services.
list_slis
Monitors SLI status and SLO compliance across all services.
get_slo
Retrieves detailed configuration for a specific SLO.
query_sampled_traces
Queries AWS X-Ray traces for distributed tracing analysis.
search_transaction_spans
Queries AWS X-Ray trace data to locate transaction spans.