AppSignal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPSIGNAL_APP_ID | Yes | Your AppSignal application ID | |
| APPSIGNAL_API_TOKEN | Yes | Your AppSignal API token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getIncidentD | – |
| getIncidentSampleD | – |
| listIncidentsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyzeIncident | |
| suggestFixes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| incidents |
TDQS
Scored across 3 tools
The tools have distinct names (getIncident, getIncidentSample, listIncidents) suggesting different purposes, but without descriptions, it's unclear how 'getIncident' and 'getIncidentSample' differ—they could overlap in retrieving incident data. The 'listIncidents' is clearly separate for listing multiple incidents.
All tool names follow a consistent camelCase pattern with clear verb-noun combinations (getIncident, getIncidentSample, listIncidents). There are no deviations in naming style, making them predictable and readable.
With only 3 tools, the server feels thin for an incident management domain, as it likely lacks essential operations like creating, updating, or resolving incidents. This minimal set may not support complete agent workflows, indicating an under-scoped tool surface.
Inferred from the domain (incident management), there are significant gaps: no tools for creating, updating, deleting, or resolving incidents, and no coverage for related entities like alerts or metrics. This incomplete surface will likely cause agent failures in handling full incident lifecycles.