MCP Server: Performance, Logs, and More

AppSignal MCP graduates from beta to preview with this release.

The AppSignal MCP server now exposes 24 tools across seven areas — up from 18 — with two new capability areas and expanded write access throughout.

What's new:

• Performance: Ask your agent which actions are slowest, pull traces for a specific action, inspect full span trees, and drill into individual spans. Works with both sample-based performance data and OpenTelemetry traces.
• Logging: Search log lines using AppSignal's expression syntax, and set up log processing rules directly from your editor: create filters, trigger alerts, extract metrics from log lines, and control execution order.
• Anomaly triggers: In addition to listing triggers and alerts, you can now create, update, and archive anomaly detection triggers without leaving your editor.
• OAuth support: The MCP server now supports OAuth authentication, which unlocks GitHub Copilot CLI support.

Token permissions now include the performance and logging toolsets alongside app, exceptions, metrics, anomalies, and dashboards.

For setup instructions and the full tool reference, see the MCP documentation. Read the full blog post for the complete breakdown.

Open backtrace lines in your local editor

Once configured, open any app code line from an exception backtrace directly in your local editor.

Before setup, the option is available in the extras menu, accessible via the there dots icon.

Set your preferred editor once per app under App Settings → Editor preferences. Each developer on your team can configure their own editor independently.

Supported editors: VS Code, Cursor, Windsurf, Zed, RubyMine, and Sublime Text.

Public MCP Endpoint

Connect AI agents to your AppSignal monitoring data — no Docker container required.

Our MCP server is now available as a hosted endpoint at https://appsignal.com/api/mcp. To generate a token, select your profile, go to Account Settings > MCP Tokens. Point your agent at the endpoint, and you're ready to go.

Once connected, your AI agent gets access to 18 tools across five areas:

• Error incidents — list, search, and bulk-update exceptions; assign team members and add investigation notes.
• Anomaly detection — browse open alerts and review trigger configurations for any metric.
• Metrics — discover available metrics, query timeseries data, and get aggregated values with tag filtering.
• Dashboards — create dashboards and add or update chart visuals from your editor.
• App discovery — find apps, environments, namespaces, users, and notifiers.

Works with Claude, Cursor, Windsurf, Zed, VS Code, and any agent that supports the MCP protocol.

For setup instructions, see the MCP documentation. Read the full blog post for more details.

More Layout Controls for Dashboards

Your dashboards now bend to your workflow — not the other way around.

• Drag-and-drop widgets

  Reposition any widget by clicking and dragging it wherever makes sense. No grid constraints, no fixed columns — place widgets freely and build a layout that matches how you actually think about your data.

• Resizable widgets

  Expand a chart that deserves more real estate. Shrink the ones that don't. Drag any widget edge to resize it and mix compact summaries with detailed graphs in the same view.

Click Edit dashboard to start reshaping your layout.

Amazon CloudWatch metrics via Amazon Data Firehose

You can now store Amazon CloudWatch metrics in AppSignal through Amazon Data Firehose.

Monitor your most critical AWS services directly from your AppSignal dashboards:

• RDS — track database connections, read/write latency and CPU utilization
• S3 — monitor bucket size, request counts and error rates
• EC2 — observe instance CPU, network traffic and disk I/O
• Lambda — keep an eye on invocations, duration and throttles
• SQS — watch queue depth, message age and processing rates
• And more!

When CloudWatch metrics are detected, we automatically create dashboards for your AWS services.

Setup only takes two steps: create a Firehose stream pointed at AppSignal and connect it to a CloudWatch metric stream. See our CloudWatch metrics documentation to get started.

Updated Log Query Syntax and Customizable Views

In the Logging Live and Explore views, we have improved the query syntax with support for nested attributes, and simplified attribute definition in queries. Existing saved views and triggers will need to be migrated to the new syntax, contact support@appsignal.com for assistance.

Read more in our Query Syntax documentation.

Log Views are now customizable

Log attributes can be added as additional columns and saved in views. Click Edit table from the options dropdown to add more columns. Click Save view to persist your customized log view.

Heroku Fir support

We've added Heroku Fir support.

By pointing Heroku Fir's telemetry drain to our collector we report the following:

• Host metrics: CPU usage, memory usage and free memory.
• Metrics from add-ons, such as PostgreSQL and Redis. These will be visible in automatically added dashboards.
• Logs from the Heroku router and API.

For more information, see the Heroku Fir sections in our Heroku documentation.

OpenTelemetry performance alerting

AppSignal supports OpenTelemetry trace data. It's now possible to set up performance alerting for traces.

In a trace summary view, click the "Add new" link in the "Triggers" box.

In the opened "New trigger" modal, configure the alerting, select your preferred notifier, and save the trigger.

It is possible to configure alerting on the mean response time of requests, and the 90th and 90th percentile of the response time. Use a warm-up to only be alerted if this continues for as long as the warm-up is configured.

Now, AppSignal will alert you about new slow actions.

Note: This only works for our OpenTelemetry tracing feature.

Vercel drains: Speed insights and traces

AppSignal supports more Vercel drains: Speed Insights and OpenTelemetry traces.

Speed Insights

Vercel Drains provide support for Web Vitals through the Speed Insights drain, like First Contentful Paint and Largest Contentful Paint. These metrics can serve as signals for delivering great user experience on the web. When Speed Insights metrics are detected, we will automatically create a "Web Vitals" dashboard for your application.

Traces

Report traces from Vercel's infrastructure to get more insights into how all parts of your application are performing. This works with our OpenTelemetry tracing feature and will report errors and performance data from your application and Vercel infrastructure (Vercel functions and edge network).

---

For more information, see these documentation pages:

• Vercel Speed Insights
• Traces from Vercel applications

New chart type: Number chart

Added a new chart type for dashboards: the number chart. The number chart displays a number on the dashboard instead of a line graph. Useful when a single value gives enough information at a glance.

The chart supports multiple ways of calculating the metric data for the timeframe selected, such as:

• Maximum value: Show the highest metric value.
• Minimum value: Show the lowest metric value.
• Average value: Show the average of the metric values.
• Total value: Show the combined value of the metric values.
• First value: Show the first metric value.
• Last value: Show the last metric value.

To add a number chart, go to your application in AppSignal, create or open a dashboard, click "Add chart", and select "Number" in the sidebar.

Markdown support for status pages and MCP updates

Added

• Add support for markdown on the AppSignal status pages. You can now use markdown in the main description, and status updates.

  

• Add get_triggers MCP Tool. This tool exposes all the anomaly detection triggers and is in preparation for the create/update trigger tool.
• Add get_app_resources MCP Tool. This tool exposes multiple application resources such as users, namespaces, and dashboards. It will be the home of application resources that do not need any additional filtering.

Removed

• Remove get_users MCP tool in favor of get_app_resources.
• Remove get_namespaces MCP tool in favor of get_app_resources.

Free plan and timezone selection for exported charts

Added

• Add free plan (See our blog post.)
• Add ability to select a timezone when exporting charts to SVG/PNG (defaults to UTC)

Fixed

• Fix bug on the notifiers page to use the correct environment selector in form.

UI Fixes and Search Improvements

Fixed

• Add a fix for a minor UI bug in the PHP and Go OpenTelemetry app installation flows.
• Ensure that in the UI, we handle the alert openedAt value being null.
• Remove the leading and trailing whitespace when submitting a search query.

Logbook Icon Fix and GitHub Integration Pagination

Added

• Add the missing icon to the logbook integration create item

Changed

• GitHub integration now fetches all repositories across multiple pages

MCP Server v1.0.0

Added

• The first release of the AppSignal MCP Server as a npm package.

View the MCP Server v1.0.0 changelog for more information.

MCP Tools for Programmatic Dashboard Management

Added

• Add MCP tools for programmatic dashboard management; Support creating dashboards, adding visuals, and updating chart configurations.

Copy error backtrace lines

Added

• Users can now copy the sample backtrace line with a click of a button. (This feature was requested in our Discord channel).

  

Fixed

• Fixed search functionality for queries containing special characters (like BSON::ObjectId('.)

MCP Anomaly Incidents

Added

• MCP get_incident tool now supports both exception and anomaly incidents

Fixed

• Ensure the graph export popover isn’t cut off when placed at the bottom of the page.

MCP and product updates

Added

• Added a link to the docs in the trace timeline overlay explaining how to add additional instrumentation
• Added Anomaly incidents MCP tool
• Added a toggle switch to show OpenTelemetry internal attributes

  

Changed

• We've changed the MCP Token UI to better reflect the allowed tools. Instead of sections that can have read/write/delete rights, we're now showing each individual tool with a checkbox for exposure.

  

Log trigger filtering

Added

• Add functionality that allows filtering log triggers by name, source, or creator.