AppSignal

Created By
AppSignal23 days ago
Overview

What is AppSignal?

AppSignal is a user-friendly, all-in-one monitoring platform designed for developers. Get metrics, traces, logs, uptime monitoring, error tracking, AI insights, and more, with support for popular languages like Ruby, Elixir, Node.js, Python, PHP, Java, and Go.


Getting Started

Connect your MCP client to AppSignal. An AppSignal account is required. If you don't have one, sign up for free.

What you can access

AppSignal MCP exposes read and write access to your monitoring data across seven areas. Each area maps to a permission you can configure when authenticating: with an MCP token, set each area to read, write, or disabled; with OAuth, all read and write tools are exposed at once.

What you get back depends on what your apps send to AppSignal. If your app is not sending logs, get_log_lines will not return anything. AppSignal MCP is a gateway to data AppSignal already has. It does not collect new data on its own.

Available now

  • Error incidents (read + write): list and search exceptions, inspect stack traces, update state and severity, assign handlers, and add notes
  • Performance (read): rank slowest actions, pull traces, walk span trees, and inspect span attributes. Sample-based for standard Ruby and Elixir apps; OpenTelemetry traces for apps sending OTel data
  • Anomaly detection (read + write): browse alerts, list existing triggers, and create, update, or archive triggers
  • Logging (read + write): query log lines with AppSignal's expression syntax, and set up log ingestion rules: filter, trigger, and metrics actions. Particularly powerful for stitching together a customer journey across log sources, errors, and traces in one prompt — see reconstructing a customer journey
  • Metrics (read): discover metric categories (including host_metrics), list metric names and tags, and pull timeseries or aggregated values
  • Dashboards (read + write): create dashboards, and add or update chart visuals
  • App discovery (read): list your applications, environments, namespaces, users, notifiers, log sources, log line actions, and deploy markers

For the full list of tools, parameters, and example prompts, see the MCP Tool Reference.

Server Config

{
  "mcpServers": {
    "appsignal": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://appsignal.com/api/mcp"
      ]
    }
  }
}
Project Info
Created At
23 days ago
Updated At
22 days ago
Author Name
AppSignal
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago