AppSignal MCP
Connect Claude, Cursor, Windsurf, Zed, VS Code, or GitHub Copilot to your errors, traces, logs, and metrics.
AppSignal CLI
Tail logs, inspect incidents, and manage triggers from your shell, in human-readable or JSON output.
Which one to use
Both reach the same data. They differ in how the agent talks to AppSignal.- MCP is a hosted HTTP endpoint at
https://appsignal.com/api/mcp. Point your editor or chat app at it once and the agent queries AppSignal directly, with no install step. Read the setup instructions for your tool and the tool reference for what it exposes. - The CLI is a single binary you run yourself. Agents drive it by running commands and reading
--output json. Use it when you want the agent working in the same shell as your tests and deploys, or when the environment restricts outbound traffic.
Teach your agent the CLI
The CLI bundles an agent skill: a set of instructions that teaches Claude, Codex, or OpenCode when to reach forappsignal-cli and how to read its output.
Shell
What agents can reach
Both surfaces read the data AppSignal already has. If your application isn’t sending logs, an agent can’t query them.- Errors and exception incidents
- Performance incidents and traces
- Logs, including saved views and log-based metrics
- Metrics and dashboards
- Anomaly detection triggers
- Applications, namespaces, and deploy markers
An agent using MCP or the CLI acts as you, with your access to your
organization’s data. Authenticate the CLI on the machine
where the agent runs, and treat MCP access the same way you treat your own.