home / mcp / appsignal mcp server

AppSignal MCP Server

AppSignal MCP protocol server

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "appsignal-appsignal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "APPSIGNAL_API_KEY",
        "appsignal/mcp"
      ],
      "env": {
        "APPSIGNAL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can run AppSignal MCP Server to expose monitoring data, metrics, and debugging tools from your editor experience. This server runs in a container and connects to your AppSignal MCP token, enabling seamless access to AppSignal’s MCP features.

How to use

Start by pulling and running the MCP server container with your AppSignal MCP token. Connect your MCP-enabled editor or tool to the server using the standard docker-based command configurations shown in each editor’s setup example. Once running, you can inspect data, view metrics, and use debugging features directly from your editor environment.

How to install

Prerequisites you need before installing the MCP Server:

Docker installed on your machine
An AppSignal account with an MCP token

Install steps you should follow to set up the MCP server:

# 1) Pull the AppSignal MCP Server image
docker pull appsignal/mcp:latest

# 2) Run the MCP server with your API key (example for a local development setup)
docker run -i --rm -e APPSIGNAL_API_KEY=your_api_key_here appsignal/mcp

Additional configuration and usage notes

You can configure multiple editor integrations to connect to the AppSignal MCP Server. Here are common editor configurations shown in concrete snippets. Each configuration uses Docker to run the MCP server and passes your API key as an environment variable.

{
  "mcpServers": {
    "appsignal": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "APPSIGNAL_API_KEY", "appsignal/mcp"],
      "env": {
        "APPSIGNAL_API_KEY": "your_api_key_here"
      }
    }
  }
}

Security and access

Protect your MCP token and never expose it in public code. Use environment variable injection or secret management supported by your editor to keep the token secure.

Troubleshooting

If you encounter connection issues, verify that Docker is running, the MCP image is pulled, and the APPSIGNAL_API_KEY environment variable is correctly set. Check editor configuration to ensure the server name matches and that the docker command is reachable from your editor.

Notes

The MCP server is in Beta. Expect updates and enhancements as you integrate it into your workflow. If you need help, join the editor-specific channels to share feedback and request features.

Development and contributing

To work on the MCP server locally, you can build and test the TypeScript sources, run the inspector tool for debugging, and follow the project’s development workflow to create changesets and release new versions.

Available tools

inspector

MCP inspector for debugging and inspecting MCP data flows.