AppSignal MCP Server

This is the official AppSignal [MCP][mcp] server. AppSignal MCP gives your AI editor direct access to your monitoring data: errors, traces, logs, metrics, and dashboards.

AppSignal MCP is a public HTTP endpoint at https://appsignal.com/api/mcp. Connect your agent to that endpoint directly. You don’t need this repository to use AppSignal MCP.

[!IMPORTANT] This repo is unmaintained. Please use the AppSignal MCP endpoint directly. This repository holds a legacy stdio proxy, published as the appsignal/mcp Docker image and the @appsignal/mcp npm package. It still works, but it is no longer the recommended way to connect and we do not plan to develop it further. Connect to https://appsignal.com/api/mcp instead. See Legacy stdio proxy if your setup needs it.

Read the full MCP reference on the AppSignal official documentation.

Join our [Discord community][discord] to help shape this MCP implementation. Feature requests are welcome!

Connect to AppSignal MCP

The endpoint authenticates with OAuth, so there is no server to install or run. In Claude Code:

claude mcp add --transport http appsignal https://appsignal.com/api/mcp

Claude Code starts the browser sign-in the first time an AppSignal tool is used. Run claude mcp list to confirm it shows as connected.

The [setup guide][docs-setup] covers the Claude app, Cursor, Devin, Zed, VS Code, GitHub Copilot CLI, Gemini CLI, and OpenAI Codex. To authenticate with an [MCP token][appsignal-mcp-token] instead of OAuth, add an Authorization: Bearer header. The setup guide shows the exact form for each editor.

What you can access

The endpoint exposes read and write tools across seven areas: error incidents, performance, anomaly detection, logging, metrics, dashboards, and app discovery. With an MCP token, you can set each area to read, write, or disabled. With OAuth, AppSignal exposes all read and write tools at once.

For the full list of tools, parameters, and example prompts, see the [MCP tool reference][docs-reference].

Legacy stdio proxy

The Docker image and npm package in this repository wrap the HTTP endpoint in a stdio transport. Use them only for agents that cannot speak HTTP MCP, or in environments that restrict outbound traffic.

This path is obsolete and we do not recommend it. It keeps working, but all new work goes into the HTTP endpoint.