Appsignal MCP Server

MCP server for AppSignal error monitoring integration

Local serverstdio

What is the Appsignal MCP MCP server?

Appsignal MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for AppSignal error monitoring integration.

What you get

A Model Context Protocol (MCP) server for AppSignal monitoring API integration. This server allows AI assistants to directly query and fetch error and performance data from AppSignal through the MCP protocol.

  • Fetch details about specific error or performance samples
  • Search for errors, performance samples, or both with flexible filters
  • Integration with AppSignal's Error and Performance Monitoring APIs

Configuration and credentials

You will need one environment variable: APPSIGNAL_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Bun runtime - AppSignal account and API token - Application ID from your AppSignal dashboard

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by pauldub; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the appsignal mcp mcp server does with a few real requests.

How to install the Appsignal MCP MCP server

{
  "mcpServers": {
    "appsignal-mcp": {
      "type": "stdio",
      "command": "bun",
      "args": [
        "run",
        "start"
      ],
      "env": {
        "APPSIGNAL_API_TOKEN": "your-api-token"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Bun runtime - AppSignal account and API token - Application ID from your AppSignal dashboard
VariableDescriptionRequired
APPSIGNAL_API_TOKENCredential the server authenticates with.Yes

Frequently asked questions

It connects Appsignal MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Appsignal MCP directly.