This MCP server integrates with AppSignal's application performance monitoring capabilities, allowing you to access alerts, search logs, and monitor your applications directly from Claude or other MCP clients.
Ensure Node.js is installed on your system. If not, download it from nodejs.org
Locate your Claude Desktop configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
Add the AppSignal MCP server configuration to your claude_desktop_config.json
file:
{
"mcpServers": {
"appsignal": {
"command": "npx",
"args": ["-y", "appsignal-mcp-server"],
"env": {
"APPSIGNAL_API_KEY": "your-api-key-here"
}
}
}
}
Replace "your-api-key-here"
with your actual AppSignal API key
Restart Claude Desktop to apply the changes
Once installed, you can use the following tools to interact with AppSignal through your MCP client:
Tool Name | Description |
---|---|
get_apps |
Lists all available AppSignal applications |
select_app_id |
Select an application ID for subsequent operations |
get_exception_incident |
Get details about a specific exception incident |
get_exception_incident_sample |
Get a sample occurrence of a specific exception |
get_log_incident |
Get details about a specific log incident |
get_anomaly_incident |
Get details about a specific anomaly incident |
search_logs |
Search application logs with flexible query parameters |
get_log_incidents |
List log incidents with optional state filtering |
get_exception_incidents |
List exception incidents with optional state filtering |
get_anomaly_incidents |
List anomaly incidents with optional state filtering |
First, get a list of your applications:
get_apps
Select an application to work with:
select_app_id app_id_from_the_list
Now you can use any of the other tools to interact with that application.
To search for logs containing a specific error message:
search_logs error:"database connection failed"
To list all open exception incidents:
get_exception_incidents state:OPEN
When using get_log_incidents
, get_exception_incidents
, or get_anomaly_incidents
, you can filter by state:
OPEN
: Active incidents requiring attentionCLOSED
: Resolved incidentsWIP
: Work-in-progress incidents being investigatedIf no state filter is provided, only OPEN incidents are returned by default.
Variable | Description | Required | Default |
---|---|---|---|
APPSIGNAL_API_KEY |
Your AppSignal API key | Yes | None |
APPSIGNAL_APP_ID |
Your AppSignal application ID | No | None |
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "appsignal" '{"command":"npx","args":["-y","appsignal-mcp-server"],"env":{"APPSIGNAL_API_KEY":"your-api-key-here"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"appsignal": {
"command": "npx",
"args": [
"-y",
"appsignal-mcp-server"
],
"env": {
"APPSIGNAL_API_KEY": "your-api-key-here"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"appsignal": {
"command": "npx",
"args": [
"-y",
"appsignal-mcp-server"
],
"env": {
"APPSIGNAL_API_KEY": "your-api-key-here"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect