AppSignal MCP

Live

API KEY

ERROR MONITORING

Monitoring

AppSignal MCP gives agents API key access to error monitoring: query incidents, read traces and logs, and manage alert triggers across your applications.

  • Per-user credentials: each call uses the actual user's token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
AppSignal MCP
agent · Acme Q3
Run
Any new exceptions in checkout since the last deploy?
S
appsignalmcp_get_exception_incidents
88ms
AppSignal agent
3 new exceptions since deploy a1f2c9. NoMethodError in CheckoutController spiked to 142 occurrences, first seen 09:14 UTC. The other 2 are single-digit.
Sources: 3 incidents, namespace web
appsignalmcp
3 incidents
18:29
Message Claude...

Tools your on-call agent reaches for on AppSignal, scoped per user.

CALL ANY TOOL
Error monitoring end to end: list exception and anomaly incidents, read logs and traces, and manage the triggers that page your team.
appsignalmcp_get_traces
Get traces
Query performance and error traces, inspect span trees, and view span details.
Parameters
Name
Type
Required
Description
app_environment
string
Required
Environment name (e.g. "production", "staging"). Not case-sensitive. Closest matches are suggested if not found.
app_name
string
Required
Name of the AppSignal application (e.g. "AppSignal" or "Project Name"). Not case-sensitive.
context
string
Required
Describe why you are calling this tool and how it fits into your overall task
action_name
string
Optional
The action name to find traces for (e.g. "BlogPostsController#index", "Sidekiq::SomeWorker#perform", "SampleTimelineQuery"). Required for performance traces. Not needed for error traces (use digest instead).
digest
string
Optional
The exception incident digest to find error traces for. Get this value from get_incident or get_exception_incidents. When provided, queries error traces instead of performance traces. Cannot be combined with namespace/action_name.
end
string
Optional
End of time range (ISO 8601 format, e.g. "2025-01-01T11:00:00Z"). Must be a complete date-time including the time of day. Defaults to now. Performance traces only.
include_sensitive
boolean
Optional
When true, includes HTTP headers, request parameters, and session data in span detail output. Only applies in span detail mode (requires span_id). Defaults to false.
limit
integer
Optional
Maximum number of traces to return (1-100, default 25). List mode only.
min_duration_ms
number
Optional
Minimum trace duration in milliseconds (performance trace list mode only). Only return traces slower than this threshold.
namespace
string
Optional
The namespace to search in (e.g. "web", "background", "graphql"). Required for performance traces. Not needed for error traces (use digest instead).
span_id
string
Optional
The span ID to inspect within a trace. Requires trace_id. Returns full span details including tags (e.g. user_id, hostname), span attributes, and timing. Use trace mode first (with trace_id, without span_id) to find span IDs.
start
string
Optional
Start of time range (ISO 8601 format, e.g. "2025-01-01T10:00:00Z"). Must be a complete date-time including the time of day. Defaults to 24 hours ago. Performance traces only.
trace_id
string
Optional
The trace ID to inspect. When provided, returns the full span tree for this trace. Combine with span_id to get detailed information about a specific span. Use list mode first (without trace_id) to find trace IDs.
appsignalmcp_get_metrics_list
Get metrics list
appsignalmcp_get_incident
Get incident
appsignalmcp_update_incidents
Update incidents
appsignalmcp_get_triggers
Get triggers
appsignalmcp_create_dashboard_visual
Create dashboard visual
appsignalmcp_get_performance
Get performance
appsignalmcp_update_dashboard_visual
Update dashboard visual
appsignalmcp_get_applications
Get applications
appsignalmcp_manage_trigger
Manage trigger
appsignalmcp_get_log_lines
Get log lines
appsignalmcp_archive_trigger
Archive trigger
appsignalmcp_get_more_tools
Get more tools
appsignalmcp_discover_metrics
Discover metrics
appsignalmcp_get_metric_tags
Get metric tags
appsignalmcp_manage_dashboard
Manage dashboard
appsignalmcp_get_metric_names
Get metric names
appsignalmcp_manage_incident_note
Manage incident note
appsignalmcp_get_app_resources
Get app resources
appsignalmcp_manage_log_line_action
Manage log line action
appsignalmcp_get_anomaly_incidents
Get anomaly incidents
appsignalmcp_reorder_log_line_actions
Reorder log line actions
appsignalmcp_get_metrics_timeseries
Get metrics timeseries
appsignalmcp_delete_log_line_action
Delete log line action
appsignalmcp_get_exception_incidents
Get exception incidents
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// AppSignal tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["appsignalmcp"], toolNames: [
    "appsignalmcp_get_exception_incidents",
    "appsignalmcp_get_incident",
    "appsignalmcp_get_traces"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Any new exceptions since the last deploy?" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["appsignalmcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Which endpoints slowed down after yesterday's deploy?" }],
  tools,
});

// Execute the tool call with the user's vaulted AppSignal credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["appsignalmcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Summarize open anomaly alerts for the web namespace." }],
  tools,
});

// Tool call runs with the user's vaulted AppSignal credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["appsignalmcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "appsignal_oncall_agent",
  model: "gemini-2.5-pro",
  instruction: "Triage AppSignal incidents for the signed-in user.",
  tools,
});

await agent.run("Assign the checkout exception spike to the payments team.");
Try these prompts
Copy any prompt into your agent. Each maps directly to an AppSignal tool. Click to copy, paste into your agent, done.
Triage errors
Copy the prompt
Copied
List open exception incidents from the last 24 hours.
Copy the prompt
Copied
Show details for incident 482 and its recent occurrences.
Copy the prompt
Copied
Which exceptions started after deploy revision a1f2c9?
Performance and logs
Copy the prompt
Copied
Trace the slowest checkout requests from this morning.
Copy the prompt
Copied
Query error-level log lines mentioning timeout in the web app.
Copy the prompt
Copied
Plot the response time timeseries for the API namespace this week.
Alerts and cleanup
Copy the prompt
Copied
Create a trigger that alerts when queue latency passes 5 seconds.
Copy the prompt
Copied
List anomaly alerts that are still open and unassigned.
Copy the prompt
Copied
Close all resolved incidents and assign the rest to on-call.
SEE HOW AUTH WORKS
Your users connect once. Their AppSignal credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
AppSignal MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
AppSignal MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
AppSignal MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
AppSignal MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other monitoring connectors.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
Test other agents
See the same per-user auth pattern across other monitoring connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared AppSignal key looks fine in a demo. In production every incident closed and trigger changed looks like one service account, and you cannot tell who silenced an alert before an outage. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
AppSignal today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access AppSignal as the user or through a shared key?
As the user. Scalekit resolves the credential of the person who triggered the agent at request time, so every incident update and trigger change in your audit trail is attributed to a real user, not a shared service account.
Where is the AppSignal API key stored?
In an AES-256 encrypted vault with per-tenant namespacing. Keys are resolved at request time, never enter LLM context, and can be rotated or revoked from one dashboard.
Can I limit what the agent does in AppSignal?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example read-only incident and trace queries without update_incidents or manage_trigger. Scalekit also enforces scope checks before every API call.
What happens when a user revokes access?
The credential is invalidated at the next tool call. The call fails closed, other users' connections are unaffected, and the revocation is logged in the audit chain.
Can the agent close incidents or change alert triggers on its own?
Only if you expose those tools. update_incidents, manage_trigger, and archive_trigger are separate tool names, so you can keep agents read-only or gate writes to specific users. Every state change is scope-checked first and logged with the user who triggered it.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""appsignalmcp"": {
""url"": ""https://mcp.scalekit.com/appsignalmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.appsignalmcp]
url = ""https://mcp.scalekit.com/appsignalmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""appsignalmcp"": {
""url"": ""https://mcp.scalekit.com/appsignalmcp"",
""type"": ""http""
}
}
}