AppSignal MCP Server
Connects to AppSignal's GraphQL API to fetch and analyze incident information, allowing users to list incidents, get incident details, retrieve error samples, and obtain AI-generated analysis and fix suggestions for application errors.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AppSignal MCP Server show me the latest incident"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-appsignal
An MCP (Model Context Protocol) server for connecting to AppSignal and fetching incident information.
Installation
npm install -g mcp-appsignalRelated MCP server: Sentry MCP Server
Usage
Command Line
# Set environment variables
export APPSIGNAL_API_TOKEN=your-api-token
export APPSIGNAL_APP_ID=your-app-id
# Run the server
mcp-appsignalWith Cursor
Add to your Cursor settings:
{
"mcp": {
"servers": {
"appsignal": {
"command": "npx",
"args": ["mcp-appsignal"],
"env": {
"APPSIGNAL_API_TOKEN": "your-api-token",
"APPSIGNAL_APP_ID": "your-app-id"
}
}
}
}
}Features
Connect to AppSignal's GraphQL API
Fetch incident details and samples
List and search incidents
Provide prompts for analyzing incidents and suggesting fixes
MCP Resources
appsignal://incident/{incidentNumber}- Get details about a specific incidentappsignal://incident/{incidentNumber}/sample/{sampleId?}- Get a sample for a specific incidentappsignal://incidents- List all incidents
MCP Tools
getIncident- Fetch an incident by numbergetIncidentSample- Fetch a sample for a specific incidentlistIncidents- List incidents with optional filtering
MCP Prompts
analyzeIncident- Analyze an incident and provide insightssuggestFixes- Suggest fixes for an error
License
MIT
Available Tools
3 toolsgetIncidentD
Inputs: incidentNumber (required).
getIncidentSampleD
Inputs: incidentNumber (required), sampleId.
listIncidentsD
Inputs: limit, state.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Model Context Protocol server for Studex tools, notifications, and profile integrations
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that retrieves and analyzes Sentry.io issues, allowing users to inspect error reports, stacktraces, and debugging information from their Sentry account.223-

Sentry MCP Serverofficial
AlicenseBqualityDmaintenanceA Model Context Protocol server that lets AI assistants interact with the Sentry API to retrieve and analyze error data, manage projects, and monitor application performance.1112ISC- AlicenseBqualityCmaintenanceA Model Context Protocol (MCP) server that enables interaction with Waroom API to retrieve incident information and postmortem details through a standardized protocol.2620 npm1MIT

DevRev MCP Serverofficial
AlicenseBqualityNot gradedmaintenanceA Model Context Protocol server that enables searching, retrieving, creating, and updating issues and tickets using DevRev APIs.1610MIT