Summary
The error data comes to the debugging session.
Filtering by exception name and action within a time window is the query you actually make when something broke overnight — and count_only answers 'how widespread is it' without pulling the samples back.
What it is
A Bun MCP server over AppSignal's Error and Performance Monitoring APIs. Two calls: fetch one sample by id, or search an application's samples with filters for type, exception name, action, time window and result count.
What you get
- One error or performance sample fetched by sampleId and appId
- Samples searched across an application — errors, performance, or both
- Filtering by exception name, and by action_id
- A time window set with since and before, as a timestamp or in ISO format
- A result limit, or count_only to get the number without the samples
Requirements
An AppSignal account, an API token in APPSIGNAL_API_TOKEN or handed over on the launch command, and the application id from your AppSignal dashboard. It runs on the Bun runtime.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary