MCP: check-in monitors, incident search, and deeper traces

AppSignal MCP now covers check-in monitors, searches incidents by keyword, and returns more from your logs and traces. Your agent can triage more deeply without switching back to the AppSignal UI.

What's new:

• Check-in monitors: Ask whether last night's export ran, and which runs were missed or late. Set up a monitor for a new cron job without leaving your editor. get_check_in_triggers and manage_check_in_trigger cover both cron and heartbeat monitors.
• Incident search: Ask for the errors you're chasing by name, instead of having your agent page through incidents to find them. get_exception_incidents takes a query parameter that matches exception and action names, case-insensitively, with * wildcards.
• Full log messages: Stack traces, JSON payloads, and long error strings now arrive intact. get_log_lines keeps the 120-character preview as the heading, then adds the full message below it, up to 2,000 characters.
• Deeper trace detail: One call now shows where a slow request spent its time. get_traces tree mode includes the root span and a duration breakdown of self time per category. Database query text comes through up to 10,000 characters, up from 500, so your agent can read the N+1 or the missing index in full.

We also consolidated three tools, which keeps the toolset short and leaves more of your agent's context free. archive_trigger moved into manage_trigger, and reorder_log_line_actions and delete_log_line_action moved into manage_log_line_action. Each now takes an action parameter. The old names still work as aliases, so existing prompts keep working.

A fix to the server/discover handshake clears most of the "Method not found" errors clients were hitting.

Missing something? Ask your agent to call get_more_tools. We read those requests, and they shape what we add to MCP next.

See the MCP tool reference for the full list of tools and parameters.