Which integrations are available for this 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.

How do I use AppSignal MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. 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.

de en es ja ko ru zh

AppSignal MCP Server

by c20020207

Overview Schema Related Servers Score Discussions

TypeScript

Remote

mcp-appsignal

An MCP (Model Context Protocol) server for connecting to AppSignal and fetching incident information.

Installation

npm install -g mcp-appsignal

Related 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-appsignal

With 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 incident
appsignal://incident/{incidentNumber}/sample/{sampleId?} - Get a sample for a specific incident
appsignal://incidents - List all incidents

MCP Tools

getIncident - Fetch an incident by number
getIncidentSample - Fetch a sample for a specific incident
listIncidents - List incidents with optional filtering

MCP Prompts

analyzeIncident - Analyze an incident and provide insights
suggestFixes - Suggest fixes for an error

License

MIT

Available Tools

3 tools

getIncidentD

ParametersJSON Schema

Name	Required	Description	Default
`incidentNumber`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

getIncidentSampleD

ParametersJSON Schema

Name	Required	Description	Default
`incidentNumber`	Yes
`sampleId`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

listIncidentsD

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`state`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0May 20, 2025
- First observedgetIncident
- First observedgetIncidentSample
- First observedlistIncidents

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.6/5.0

Disambiguation3/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Sentry AOAuth
dev.sentry.mcp
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Monitoring Developer Tools Observability
3
Apideck MCP A
dev.apideck.mcp
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
Developer Tools
42
Studex MCP ServerOAuth
io.github.itshivams
Model Context Protocol server for Studex tools, notifications, and profile integrations
Developer Tools
1
l0-py-blocks-mcp A
io.github.SELISEdigitalplatforms
A Model Context Protocol (MCP) server for Selise Blocks Cloud integration
Cloud Platforms Developer Tools App Automation
362

Related MCP Servers

MCP Sentry
Monitoring Databases
MCP-100
F
license
B
quality
D
maintenance
A 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.
Updated a year ago (2025-07-18 09:02 UTC)
2
22
-
Sentry MCP Serverofficial
Monitoring Observability
getsentry
F
license
B
quality
F
maintenance
A 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.
Updated a year ago (2025-04-18 16:13 UTC)
11
11
-
Waroom MCP
RAG Systems
topotal
A
license
B
quality
C
maintenance
A Model Context Protocol (MCP) server that enables interaction with Waroom API to retrieve incident information and postmortem details through a standardized protocol.
Updated 2 months ago (2026-07-17 06:31 UTC)
26
42
1
MIT
DevRev MCP Serverofficial
Project Management Customer Support
devrev
A
license
B
quality
Not graded
maintenance
A Model Context Protocol server that enables searching, retrieving, creating, and updating issues and tickets using DevRev APIs.
Updated 8 months ago (2026-01-21 14:33 UTC)
16
10
-

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/c20020207/mcp-appsignal'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

mcp-appsignal

Installation

Usage

Command Line

With Cursor

Features

MCP Resources

MCP Tools

MCP Prompts

License

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

MCP Sentry

Sentry MCP Serverofficial

Waroom MCP

DevRev MCP Serverofficial

Latest Blog Posts

MCP directory API