A CLI for humans and agents
One static binary, one auth, one JSON shape. It doesn't care whether you typed the command or your agent did — the same monoscope drives shell sessions, CI pipelines, and any LLM that can run bash.
A real incident, in three commands
# 1. Which service is on fire?
monoscope facets resource.service.name --top 3
# 2. Get one error to anchor the investigation.
ID=$(monoscope logs search 'severity.text=="error"' \
--service checkout-api --since 1h --first --id-only)
# 3. Pull the surrounding 5 minutes — every trace, every service touched.
monoscope events context --window 5m --summary \
--at "$(monoscope events get "$ID" | jq -r .timestamp)"
Every command emits stable JSON, surfaces the server’s actual error
message (not an opaque 4xx), and switches into agent mode under
MONOSCOPE_AGENT_MODE=1 — auto-set in CI, where the same binary backs
assertions like monoscope metrics query '...' --assert '< 0.01'.
Three surfaces, one product
For your terminal
monoscope CLI
A single static binary for shell or CI. Tabular output for humans, JSON for pipes. The tool everything else on this page wraps.
For any MCP client
MCP Server
Hosted endpoint, ~50 tools, no install. Wire any agent in over the network.
For Claude Code
Agent Skills
Drop-in
investigate, triage, kql-reference — natural language to CLI calls.
curl monoscope.tech/install.sh | sh — drops the binary into ~/.local/bin. Linux and macOS, x86_64 and arm64.