Appsignal MCP server

Read from the package source without running it. The installed server may list more.

• custom_graphql_querywrite action

  Execute a custom GraphQL query against the AppSignal API. This is a powerful escape hatch for accessing data not available through the specialized tools. IMPORTANT: Before using this tool: 1. Call get_graphql_schema to understand available types and queries 2. Call get_graphql_schema_details with relevant type names to see field definitions 3. Construct your query based on the schema The AppSignal

• get_anomaly_incident

  Retrieve detailed information about a specific anomaly incident in your AppSignal application. Anomaly incidents are automatically detected unusual patterns in your application's performance metrics, such as abnormal response times, memory usage spikes, or throughput variations. This tool provides comprehensive details about a single anomaly, including when it was detected, its severity, affected

• get_anomaly_incidents

  Retrieve a list of anomaly incidents detected by AppSignal's automatic performance monitoring. Anomaly incidents represent unusual patterns in your application's behavior, such as response time spikes, memory usage anomalies, or throughput variations. This tool allows filtering by incident state and supports pagination for large result sets. Example response: { "incidents": [ { "id": "anomaly-123"

• get_apps

  Retrieve a list of all available AppSignal applications associated with your account. This tool is essential for discovering which applications you can monitor and must be used before selecting a specific app to work with. Returns an array of application objects containing details like app ID, name, environment, and other metadata. This is typically the first tool you'll use when starting an AppSi

• get_deploy_markerswrite action

  Retrieve recent deployment markers from AppSignal to correlate performance issues and incidents with code deployments. This tool is essential for understanding whether a spike in errors or performance degradation coincides with a recent deployment. Each marker includes revision information, deployment time, the user who deployed, and exception counts that occurred after the deployment. Example res

• get_exception_incident

  Retrieve detailed information about a specific exception incident in your AppSignal application. Exception incidents represent errors, crashes, or unhandled exceptions that occurred in your application. This tool provides comprehensive details about a single exception, including the error message, stack trace, occurrence count, affected users, and environment context. Example response: { "id": "ex

• get_exception_incident_sample

  Retrieve sample data for a specific occurrence of an exception incident. While exception incidents group similar errors together, this tool provides context of a single occurrence, including request parameters, session data, and environment details. Note: Due to API limitations, the actual exception message and backtrace are not available. 💡 Recommended follow-up: After retrieving the sample, use

• get_exception_incidents

  Retrieve a list of exception incidents from your AppSignal application. Exception incidents group similar errors together, showing patterns of application crashes, errors, and unhandled exceptions. This tool provides an overview of all exception types affecting your application, with filtering and pagination capabilities. Example response: { "incidents": [ { "id": "exc-789", "error": "ActiveRecord

• get_graphql_schema

  Returns a summary of the AppSignal GraphQL API schema, including available Query fields, Mutation fields, and all type definitions with their names, kinds, and descriptions. This is a discovery tool - use it BEFORE constructing a custom_graphql_query to understand what data is available. The summary provides: - Query fields: What data you can fetch (app, organization, viewer, timezones) - Mutation

• get_graphql_schema_details

  Returns full GraphQL type definitions for the specified type names. Use this after get_graphql_schema to get detailed field information for types you need in your custom query. This tool provides the complete schema definition including: - All fields with their types and arguments - Field descriptions and documentation - Enum values - Interface implementations - Input object fields Example usage:

• get_log_incident

  Retrieve detailed information about a specific log incident in your AppSignal application. Log incidents represent patterns in your application logs that indicate potential issues, such as repeated error messages, warning patterns, or critical system events. This tool provides comprehensive details about a single log incident including the log pattern, frequency, and context. Example response: { "

• get_log_incidents

  Retrieve a list of log incidents from your AppSignal application. Log incidents are automatically detected patterns in your application logs that may indicate issues, such as repeated errors, warnings, or critical events. This tool provides an overview of all log patterns requiring attention, with filtering and pagination support. Example response: { "incidents": [ { "id": "log-789", "pattern": "R

• get_metrics

  Retrieve aggregated performance metrics from AppSignal for your application. This tool provides statistical insights into application performance including mean response times, P95 (95th percentile), and request counts. Essential for understanding application performance trends, identifying slowdowns, and monitoring system health over time. The tool returns metrics aggregated across the specified

• get_metrics_timeseries

  Retrieve time-series metrics data from AppSignal showing how metrics change over time. This tool returns data points with timestamps, useful for identifying performance trends, spikes, or degradations over a specified time window. The tool retrieves both MEAN (average) and P95 (95th percentile) values for each data point, allowing you to see typical performance as well as worst-case scenarios. Thi

• get_perf_incident

  Retrieve details about a specific performance incident from AppSignal. Performance incidents represent specific performance bottlenecks like slow endpoints, database queries, or external API calls. This tool provides detailed information about a single performance issue. Example response: { "id": "perf-123", "number": "42", "state": "open", "severity": "high", "actionNames": ["UsersController#show

• get_perf_incident_sample

  Retrieve a sample transaction for a specific performance incident from AppSignal. Samples provide detailed timing information about a specific slow request or operation, helping you understand exactly where time is being spent. 💡 Recommended follow-up: After retrieving the sample, use the search_logs tool with: - Time range around the sample's timestamp (-10 seconds through +3 seconds) - Query te

• get_perf_incident_sample_timeline

  Retrieve the detailed timeline for a performance incident sample from AppSignal. The timeline shows a hierarchical breakdown of all operations performed during a request, including database queries, view rendering, external API calls, and custom instrumentation. This is essential for identifying the exact bottlenecks in slow requests. Example response: { "sampleId": "sample-789", "timeline": [ { "

• get_perf_incidents

  Retrieve a list of performance incidents from your AppSignal application. Performance incidents identify slow endpoints, database queries, and other performance bottlenecks in your application. This tool provides an overview of all performance issues affecting your application, with filtering and pagination capabilities. Example response: { "incidents": [ { "id": "perf-123", "number": "42", "state

• get_perf_samples

  Retrieve multiple recent performance samples for a specific controller action from AppSignal. Each sample represents a detailed snapshot of a slow request or operation, including timing breakdowns by component (database, view rendering, etc.), request parameters, and the full execution path. This tool provides broader context by showing multiple examples of the same performance issue, helping you

• get_slow_requests

  Convenience tool that retrieves the slowest recent requests from your AppSignal application in a single call. This combines performance incident data with detailed sample information to quickly identify and analyze performance bottlenecks. For each slow incident, you get: - Incident overview: action names, mean duration, occurrence count, namespace - N+1 query detection - Sample requests with: - F

• search_logs

  Search through application logs in AppSignal with powerful filtering capabilities. This tool allows you to query logs by content, filter by severity levels, and retrieve recent log entries matching your criteria. It's essential for troubleshooting specific issues, analyzing application behavior, and investigating error conditions. Note that it can be very helpful to use start/end parameters around

• Code scan103 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 27 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

85/100

higher than 75% of 3,470 Web search servers

Tools

21

the typical Web search server has 5

Tools that change things

10%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

80

more than 94% of 1,786 Web search servers

Appsignal: common questions

Is Appsignal MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the Appsignal safety report

How do I install Appsignal?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Appsignal need an API key?

Yes. The registry entry asks for APPSIGNAL_API_KEY.

Is Appsignal maintained?

The last commit was 66 days ago (2026-08-30). The latest release is v0.5.4.

What can I use instead of Appsignal?

Servers from other publishers that do the same job: Arxiv MCP server and HasData Yelp MCP server.

How does Appsignal compare with other Web search MCP servers?

safety score 85/100 (higher than 75% of 3,470 Web search servers); tools 21 (the typical Web search server has 5); tools that change things 10% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.