Appsignal

Name: Appsignal
Author: pulsemcp

by pulsemcpversion 0.5.4i★ –iRuns on your computer

Registry namecom.pulsemcp/appsignal

Install

Overview

Description from the maker (original English)

MCP server for AppSignal — get alert details, search logs, and retrieve logs within time ranges.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: APPSIGNAL_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: APPSIGNAL_API_KEY, APPSIGNAL_APP_ID

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "appsignal": {
      "command": "npx",
      "args": [
        "-y",
        "appsignal-mcp-server"
      ],
      "env": {
        "APPSIGNAL_API_KEY": "your-value",
        "APPSIGNAL_APP_ID": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add appsignal --env APPSIGNAL_API_KEY=your-value --env APPSIGNAL_APP_ID=your-value -- npx -y appsignal-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "appsignal": {
      "command": "npx",
      "args": [
        "-y",
        "appsignal-mcp-server"
      ],
      "env": {
        "APPSIGNAL_API_KEY": "your-value",
        "APPSIGNAL_APP_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "appsignal": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "appsignal-mcp-server"
      ],
      "env": {
        "APPSIGNAL_API_KEY": "your-value",
        "APPSIGNAL_APP_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

APPSIGNAL_API_KEY secret required env
Your AppSignal API key for authentication.
APPSIGNAL_APP_ID env
Your AppSignal application ID (optional; can be selected dynamically).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain pulsemcp.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7277 servers in this category
Published to the registry more recently than 17% of the other 7277 servers in this category
Basic checks equal to or better than 100% of the other 7277 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Appsignal safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: APPSIGNAL_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.4) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AppSignal MCP Server

Haven't heard about MCP yet? The easiest way to keep up-to-date is to read our weekly newsletter at PulseMCP.

This is an MCP (Model Context Protocol) Server integrating MCP Clients with AppSignal's application performance monitoring and error tracking capabilities: get alert details, search logs, and retrieve logs within specific time ranges.

AppSignal is a comprehensive APM (Application Performance Monitoring) solution that helps developers monitor their applications' performance, track errors, and debug issues. This server connects directly to their REST API. You will need to sign up for an API Key from AppSignal to get started.

This project is NOT officially affiliated with AppSignal.

Highlights
Capabilities
Usage Tips
Examples
Setup
Cheatsheet
Claude Desktop
Manual Setup

Highlights

Real-time monitoring integration: Access your application's alerts, errors, and logs directly within Claude or other MCP clients, enabling seamless debugging and monitoring workflows.

Powerful log searching: Search through your application logs with flexible query options, making it easy to find specific issues or patterns.

Time-based log retrieval: Retrieve logs within specific datetime ranges for focused analysis of incidents or debugging time-sensitive issues.

Zero context switching: No need to leave your conversation to check alerts or search logs - everything is integrated directly into your MCP client.

Capabilities

This server is built and tested on macOS with Claude Desktop. It should work with other MCP clients as well.

Tool Name	Description
`get_apps`	Get a list of all available AppSignal applications.
`select_app_id`	Select an AppSignal application ID to use for subsequent operations.
`get_exception_incident`	Get detailed information about a specific exception incident.
`get_exception_incident_sample`	Get a sample occurrence of a specific exception incident.
`get_log_incident`	Get detailed information about a specific log incident.
`get_anomaly_incident`	Get detailed information about a specific anomaly incident.
`search_logs`	Search through application logs with flexible query parameters and filters.
`get_log_incidents`	Get a list of log incidents with optional state filter (OPEN, CLOSED, WIP).
`get_exception_incidents`	Get a list of exception incidents with optional state filter (OPEN, CLOSED, WIP).
`get_anomaly_incidents`	Get a list of anomaly incidents with optional state filter (OPEN, CLOSED, WIP).

Usage Tips

All log searches support flexible query syntax - you can search for exact phrases, keywords, or use AppSignal's query language
Alert IDs can be found in your AppSignal dashboard or through alert notifications
Use the tools in combination to investigate issues - get alert details first, then search related logs
The list tools (get_log_incidents, get_exception_incidents, get_anomaly_incidents) support filtering by state:
OPEN: Active incidents requiring attention
CLOSED: Resolved incidents
WIP: Work-in-progress incidents being investigated
By default, list tools return only OPEN incidents if no state filter is provided

Development

Testing

This project uses Vitest for unit testing. Tests are automatically run on pull requests and pushes to the main branch.

Running Tests Locally

# Install dependencies

npm run install-all

Run tests once

npm run test:run

Run tests in watch mode (recommended for development)

npm test

Run tests with UI

npm run test:ui

Test Structure

Tests are located in the tests/ directory:

tests/functional/ - Functional tests for individual components
tests/integration/ - Integration tests with mocked AppSignal API
tests/manual/ - Manual tests that hit the real AppSignal API (not run in CI)
tests/mocks/ - Mock implementations and test data

See tests/README.md for more details on the testing approach.

Manual Testing

Manual tests are end-to-end system tests that verify the complete integration with the real AppSignal API. These tests:

Require real API credentials (APPSIGNAL_API_KEY environment variable)
Hit the actual AppSignal production API - not mocked
Chain together real API calls in a realistic workflow
Are not run in CI to avoid API rate limits and dependency on external services
Should be run when modifying AppsignalClient code or any code that interacts with the external API

The manual test suite follows this workflow:

Lists all available apps using your API key
Automatically selects the first app
Searches for logs in that app
Tests various search patterns and error scenarios
Provides detailed console output showing the actual API responses

To run manual tests:

# Copy .env.example to .env and add your API key

cp .env.example .env

Edit .env to add your real API key

Run manual tests

npm run test:manual

Run manual tests in watch mode

npm run test:manual:watch

Test Outcomes:

SUCCESS ✅ - All critical tests passed, full happy path completed
WARNING ⚠️ - Core functionality works but some features couldn't be fully validated (e.g., no data available or API limitations)
FAILURE ❌ - Verifiable breakage in the integration

The tests automatically adapt to your AppSignal data and API limitations.

Setup

Prerequisites

Node.js v24.2.0 (use nvm use if you have nvm installed)
An AppSignal API key

Cheatsheet

Environment Variable	Description	Required	Default Value	Example
`APPSIGNAL_API_KEY`	Your AppSignal API key. Get one at appsignal.com	Y	N/A	`your-api-key-here`
`APPSIGNAL_APP_ID`	Your AppSignal application ID	N	N/A	`5f3e4d2c1b0a9f8e7d6c5b4a`

Claude Desktop

Make sure you have an API key from AppSignal and your application ID ready.

Then proceed to your preferred method of configuring the server below. If this is your first time using MCP Servers, you'll want to make sure you have the Claude Desktop application and follow the official MCP setup instructions.

Manual Setup

You're going to need Node working on your machine so you can run npx commands in your terminal. If you don't have Node, you can install it from nodejs.org.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Modify your claude_desktop_config.json file to add the following:

"mcpServers": { "appsignal": { "command": "npx", "args": ["-y", "appsignal-mcp-server"], "env": { "APPSIGNAL_API_KEY": "your-api-key-here" } } } }

Restart Claude Desktop and you should be ready to go!

Appsignal

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

AppSignal MCP Server

Table of Contents

Highlights

Capabilities

Usage Tips

Development

Testing

Running Tests Locally

Run tests once

Run tests in watch mode (recommended for development)

Run tests with UI

Test Structure

Manual Testing

Edit .env to add your real API key

Run manual tests

Run manual tests in watch mode

Setup

Prerequisites

Cheatsheet

Claude Desktop

Manual Setup