Skip to main content
Observability · statuslines · 18 picks

Agent observability and status workflows

Statuslines, tools, hooks, and MCP servers for usage tracking, cost awareness, latency, health checks, and runtime visibility.

Curated by @heyclaude-editors Updated 2026-07-18

Statuslines, tools, hooks, and MCP servers for usage tracking, cost awareness, latency, health checks, and runtime visibility.

Compared at a glance

The top 5 picks side by side on trust, install, platform support, and disclosed notes — full rationale for each below.

2 trust signals differ across this comparison (Package trust, Source provenance).

Next steps differ across picks — use the actions in the table below to copy install commands and source links per resource.

Field

Claude Code statusline that reads the active model identifier from session input and displays real-time token usage as a percentage of the context window, with green/yellow/red color-coded warnings.

Open dossier

Monitor errors, debug production issues, and track application health

Open dossier

Docker statusline configuration for Claude Code CLI. Features real-time health monitoring, color-coded indicators, and container tracking. Production-ready.

Open dossier

Real-time AI cost tracking statusline with per-session spend analytics, model pricing, and budget alerts

Open dossier

Comprehensive AWS cloud services integration for infrastructure management, deployment, and monitoring

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage not verifiedPackage verifiedPackage not verifiedPackage not verifiedPackage verified
Source provenanceDiffersSource-backedNo submission linkSource-backedSource-backedNo submission link
Submitter
Install riskReview firstLow riskReview firstReview firstLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandSentry logoSentryDocker logoDockerAWS logoAWS
Categorystatuslinesmcpstatuslinesstatuslinesmcp
SourceSource-backedFirst-partySource-backedSource-backedFirst-party
AuthorJSONboredSentryJSONboredJSONboredAWS Labs
Added2025-10-162025-09-182025-10-192025-10-162025-09-16
Platforms
Harness
Source repo
Safety notesReads session JSON from stdin and writes formatted text to stdout only; does not modify files or make network calls.Scope Sentry org and project access, and review issue updates or alert changes before using it on production monitoring.Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session.Scope AWS credentials to the intended accounts, regions, and services because infrastructure actions can affect production resources.
Privacy notesProcesses token counts and model identifiers from the local Claude Code session input; no data is sent externally.Stack traces, logs, release data, user context, event payloads, and project metadata may be sent through model context.Reads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine.Reads the Claude Code statusline JSON from stdin (model, token usage, and cost) and renders it in the local terminal; it does not send data off-machine.AWS resource names, configuration, metrics, logs, ARNs, and account metadata may be exposed through tool calls and responses.
Prerequisites
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for pattern matching with [[ ]] and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • awk command (for percentage calculation with floating point precision)
  • Sentry account (free or paid plan)
  • OAuth authentication setup (via mcp.sentry.dev)
  • Network access to mcp.sentry.dev (HTTPS required)
  • Understanding of Sentry concepts (organizations, projects, events, issues)
  • Docker Engine installed and running (Docker 17.05+ recommended for health check support)
  • Bash shell available (bash 4.0+ recommended for arithmetic operations and string manipulation)
  • Docker CLI accessible in PATH (docker command must be available)
  • User permissions to run docker commands (user must be in docker group on Linux or have Docker Desktop access on macOS/Windows)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for pattern matching, arithmetic operations, and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • awk command (for floating point cost calculation with printf - preferred method)
  • Python 3.8+ installed for running uvx commands
  • uv package manager installed (provides uvx command for running Python packages)
  • AWS account with active credentials and appropriate IAM permissions
  • AWS credentials configured via one of: IAM access keys (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY), AWS profile (~/.aws/credentials), or IAM role (for EC2/ECS)
Install
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp && claude mcp list
uvx awslabs.core-mcp-server@latest && claude mcp list
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/multi-provider-token-counter.sh",
    "refreshInterval": 1000
  }
}
{
  "mcpServers": {
    "sentry": {
      "url": "https://mcp.sentry.dev/mcp",
      "type": "http"
    }
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/docker-health-statusline.sh",
    "refreshInterval": 2000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/real-time-cost-tracker.sh",
    "refreshInterval": 1000
  }
}
{
  "mcpServers": {
    "aws": {
      "env": {
        "AWS_REGION": "${AWS_REGION:-us-east-1}",
        "AWS_PROFILE": "${AWS_PROFILE}",
        "FASTMCP_LOG_LEVEL": "${FASTMCP_LOG_LEVEL:-ERROR}"
      },
      "args": [
        "awslabs.core-mcp-server@latest"
      ],
      "command": "uvx",
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool
  1. 01
    Why it made the cut

    Multi Provider Token Counter - Statuslines is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  2. 02
    Why it made the cut

    Sentry MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  3. 03
    Why it made the cut

    Claude Code Docker Statusline - Container Health Monitoring is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  4. 04
    Why it made the cut

    Real Time Cost Tracker - Statuslines is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  5. 05
    Why it made the cut

    AWS Services MCP Server - MCP Servers is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  6. 06
    Why it made the cut

    AWS CloudWatch MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  7. 07
    Why it made the cut

    Axiom MCP Server for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  8. 08
    Why it made the cut

    Datadog MCP Server for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  9. 09
    Why it made the cut

    Dynatrace MCP Server for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  10. 10
    Why it made the cut

    Honeycomb MCP Server for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  11. 11
    Why it made the cut

    Pydantic Logfire MCP Server for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  12. 12
    Why it made the cut

    AI Model Performance Dashboard - Statuslines is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  13. 13
    Why it made the cut

    Burn Rate Monitor - Statuslines is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  14. 14
    Why it made the cut

    AgentOps is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  15. 15
    Why it made the cut

    AnomalyArmor MCP Server for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  16. 16
    Why it made the cut

    API Latency Breakdown - Statuslines is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  17. 17
    Why it made the cut

    Claude Code Analytics Burn Statusline is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  18. 18
    Why it made the cut

    InfluxDB 3 MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

Missing a pick? Propose an edit to this list — every change goes through the same review queue as new entries.

Suggest a pick
Weekly · Sundays

Get the weekly brief

One calm read on Claude workflows. Sundays. No tracking pixels.

Unsubscribe any time. No tracking pixels. No partner blasts.