Our new AppSignal CLI brings your monitoring data into the terminal. Tail logs, triage incidents, manage dashboards and anomaly detection triggers, and turn logs into metrics, all without leaving the shell where you run your tests and deploys.

It's built for people and AI agents. Every command returns human-readable output or JSON (--output json), so the same tool you reach for during an incident can also feed structured data to a coding agent. The CLI also bundles an agent skill for Claude, Codex, and OpenCode.

Sign in with OAuth and you're ready to go:

appsignal-cli auth login

Install it with Homebrew (brew install appsignal/appsignal-cli/appsignal-cli) or the install script, then read the documentation to get started.

Changed

• apps list now uses the current OAuth account to determine the organization automatically and saves that org to the active config. You no longer need to pass --org when listing apps for the signed-in account.
• incidents update now accepts multiple incident numbers for bulk state changes, so you can close or reopen an explicit set of incidents in one command. It also adds --assign-me to assign the incident to the authenticated CLI user without needing to look up your user ID first.
• OAuth login now requests the user:read scope needed for browser-based AppSignal account access, and older tokens now produce a clearer re-authentication message when that scope is missing. The unsupported apps orgs command has been removed.
• Added dashboard management commands to list, create, and update AppSignal dashboards from the CLI.
• appsignal-cli now sends a minimal best-effort telemetry event for each command run to help measure CLI usage and reliability. The event includes only the command path, success or failure, duration, CLI version, and output format, and you can disable it entirely with APPSIGNAL_CLI_TELEMETRY=0.
• OAuth is now the default auth login flow, so running appsignal-cli auth login opens the browser-based sign-in flow without requiring --oauth. Personal token login remains available by passing --token explicitly.

Removed

• OAuth is now the default authentication method. appsignal-cli auth login opens the browser flow directly, while personal API token login remains available with --token.

View the CLI v2.0.0 changelog for more information.

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.

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.

Added

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

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

Added

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

Added

• Add the create_incident_note tool for the MCP server. This allows AI Agents to comment on incidents.

  

Changed

• The update_incident MCP Tool now accepts severity as an argument (and sets the severity accordingly).

Added

• Dedicated MCP authentication tokens. Instead of providing your personal AppSignal API key, that has access to all your organizations and applications, we're moving to a dedicated MCP authentication token.

  This token can be scoped to a specific organization and one or more applications. It also has permissions per "toolset", such as error incidents, metrics, and other sections of AppSignal.

  

  See our documentation for more information on installing the AppSignal MCP Server.

Added

• Debug your exceptions with the help of AI Agents through our AppSignal MCP Server.

  

  The MCP server is currently in beta, and we're focusing on (local) debugging of error incidents at this stage.

  MCP server endpoints available at this moment are:

  • get_namespaces, which can be filtered by app, and returns a list of namespaces to be used with the get_exception_incidents endpoint
  • get_users, which can be filtered by app, and returns a list of users to be used with the update_incident endpoint
  • get_exception_incidents, which can be filtered by app/namespace/status, and returns a list of incidents
  • get_incident returns detailed incident information
  • update_incidents (bulk) updates an incident with the assigned user and state

  See our documentation for more information on installing the AppSignal MCP Server.