appsignal

The AppSignal MCP server provides access to AppSignal’s monitoring data, metrics, and debugging tools directly inside your editor. Running the Docker image exposes an MCP endpoint you can connect to from supported IDEs and code editors, allowing you to browse AppSignal traces, metrics, and debugging utilities without leaving your workspace. The server is designed to be used in beta, and you’ll need to supply your AppSignal MCP API token to authenticate. Once connected, you can explore AppSignal data, run diagnostics, and use the built-in MCP inspector and related tooling to investigate performance and error data from your apps.

To enable it in your editor, configure the MCP server with the docker command provided in the docs (docker run -i --rm -e APPSIGNAL_API_KEY appsignal/mcp) and set APPSIGNAL_API_KEY to your token. Some editors provide dedicated UI panels or commands to add this MCP server; for example, Claude, Cursor, Windsurf, Zed, and VSCode have specific configuration snippets you can copy into their respective config files. After setup, your editor’s MCP features will communicate with AppSignal to fetch monitoring data and expose debugging interfaces.

The server focuses on enabling AppSignal’s monitoring tooling in the editor environment, so you can inspect metrics, traces, and performance data in context while coding, testing, or troubleshooting. You’ll typically use it alongside your existing AppSignal account to authenticate and access your own applications’ data through the MCP interface.

Prerequisites:

• Docker installed on your machine
• An AppSignal account and an MCP API token

Installation steps:

1. Pull the AppSignal MCP Docker image: docker pull appsignal/mcp:latest

2. Run the MCP server with your API key: docker run -i --rm -e APPSIGNAL_API_KEY=your_api_key_here appsignal/mcp

3. Connect your editor to the running MCP server using the provided configuration snippet (see README for editor-specific setup). Typically you’ll reference the docker command shown in the configuration examples and supply your APPSIGNAL_API_KEY as an environment variable.

4. In editors like Claude, Cursor, Windsurf, Zed, or VSCode, add the MCP server configuration to the appropriate config file or UI, pointing to the running docker container with the APPSIGNAL_API_KEY env var.

Notes:

• You may choose to pin a specific version or tag instead of latest if you require stability.
• Ensure network access from your editor to the Docker container if you run with a local Docker daemon.

Tips and gotchas:

• Always supply APPSIGNAL_API_KEY to authenticate with AppSignal MCP. Treat this as a sensitive credential.
• The server is currently in Beta; features may change and some editors’ integrations may have nuances in how they load MCP servers.
• If you encounter connection issues, verify that Docker is running and that the container can be reached from your editor, and double-check that the APPSIGNAL_API_KEY environment variable is correctly set.
• You can configure multiple editors to connect to the same MCP server by providing the same docker run command (or by running the container once and exposing it as a reachable endpoint, depending on your environment).
• The documentation also mentions various editor-specific config templates (Claude, Claude Code, Cursor, Windsurf, Zed, VSCode); use the corresponding snippet from the README to ensure proper integration.
• This MCP server pulls AppSignal data for debugging and monitoring inside the editor workflow, streamliningissues triage and performance investigations during development.