Skip to main content
statuslinesSource-backedReview first Safety Privacy

MCP Server Status Monitor - Statuslines

Real-time MCP server monitoring statusline showing connected servers, active tools, and performance metrics for Claude Code MCP integration

by JSONbored·added 2025-10-16·
HarnessClaude Code
Language:bash
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://code.claude.com/docs/en/statusline, https://github.com/JSONbored/awesome-claude/blob/main/content/statuslines/mcp-server-status-monitor.mdx
Safety notes
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.
Privacy notes
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.
Author
JSONbored
Claim status
unclaimed
Last verified
2025-10-16

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Config edit

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

6 to clear

Platforms

1 listed

Difficulty

3/100

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup.

0/6 ready
Install & runtime1Configuration1Network & hosting2General2

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 1 risk area. Review closely: credentials & tokens.

1 area
  • SafetyCredentials & tokensRuns 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.
  • PrivacyCredentials & tokensReads 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.

Safety notes

  • 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.

Privacy notes

  • 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.

Prerequisites

  • Claude Code CLI installed and configured with MCP support
  • Bash shell available (bash 4.0+ recommended for associative arrays and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • base64 command (usually pre-installed, required for base64 encoding/decoding of server data)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded connection status)
  • MCP servers configured in ~/.mcp.json or via Claude Code MCP configuration (statusline reads from Claude Code context)

Schema details

Install type
config
Reading time
1 min
Difficulty score
3
Troubleshooting
Yes
Breaking changes
No
Skill and platform metadata
Retrieval sources
https://code.claude.com/docs/en/statusline
Runtime and command metadata
Script language
bash
Script body
#!/usr/bin/env bash

# MCP Server Status Monitor
# Shows connected MCP servers and active tools

read -r input

# Extract MCP server info (if available in Claude Code context)
mcp_servers=$(echo "$input" | jq -r '.mcp.servers // []' 2>/dev/null || echo "[]")
server_count=$(echo "$mcp_servers" | jq 'length' 2>/dev/null || echo "0")

# Count active tools across all servers
active_tools=0
for server in $(echo "$mcp_servers" | jq -r '.[] | @base64'); do
  tools=$(echo $server | base64 -d | jq '.tools | length' 2>/dev/null || echo "0")
  active_tools=$((active_tools + tools))
done

# Color based on server status
if [ "$server_count" -gt 0 ]; then
  color="\033[32m"  # Green - servers connected
  icon="🔌"
else
  color="\033[90m"  # Gray - no servers
  icon="⚫"
fi

# List server names
server_names=$(echo "$mcp_servers" | jq -r '.[].name' 2>/dev/null | tr '\n' ',' | sed 's/,$//')

# Output
if [ "$server_count" -gt 0 ]; then
  echo -e "${icon} MCP ${color}${server_count}${color}\033[0m servers │ ${active_tools} tools │ ${server_names:0:30}"
else
  echo -e "${icon} MCP ${color}disconnected${color}\033[0m"
fi
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-server-status-monitor.sh",
    "refreshInterval": 2000
  }
}

About this resource

Features

  • Real-time connected server count
  • Active tools aggregation across all servers
  • Server name display with truncation
  • Color-coded connection status
  • Performance-optimized JSON parsing
  • Graceful fallback when MCP unavailable
  • Tool category breakdown (database, filesystem, API, etc.)
  • Server health monitoring with error detection

Use Cases

  • Monitoring MCP server connectivity during development
  • Tracking available tools across connected servers
  • Debugging MCP connection issues
  • Verifying server plugin installations
  • Multi-server workflows requiring tool availability awareness
  • Troubleshooting MCP integration problems with real-time status

Requirements

  • Claude Code CLI installed and configured with MCP support
  • Bash shell available (bash 4.0+ recommended for associative arrays and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • base64 command (usually pre-installed, required for base64 encoding/decoding of server data)
  • Terminal with ANSI color code support (256-color mode recommended for color-coded connection status)
  • MCP servers configured in ~/.mcp.json or via Claude Code MCP configuration (statusline reads from Claude Code context)

Configuration

{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-server-status-monitor.sh",
    "refreshInterval": 2000
  }
}

Examples

Enhanced MCP Server Status Monitor with Health Checks

Extended version checking individual server health and connection status

#!/usr/bin/env bash

# Enhanced MCP Server Status Monitor with Health Checks

input=$(cat)

mcp_servers=$(echo "$input" | jq -r '.mcp.servers // []' 2>/dev/null || echo "[]")
server_count=$(echo "$mcp_servers" | jq 'length' 2>/dev/null || echo "0")

active_tools=0
healthy_servers=0
unhealthy_servers=0

if [ "$server_count" -gt 0 ]; then
  for server in $(echo "$mcp_servers" | jq -r '.[] | @base64'); do
    decoded=$(echo "$server" | base64 -d 2>/dev/null || echo "{}")
    tools=$(echo "$decoded" | jq '.tools | length // 0' 2>/dev/null || echo "0")
    status=$(echo "$decoded" | jq -r '.status // "unknown"' 2>/dev/null || echo "unknown")

    active_tools=$((active_tools + tools))

    if [ "$status" = "connected" ] || [ "$status" = "healthy" ]; then
      healthy_servers=$((healthy_servers + 1))
    else
      unhealthy_servers=$((unhealthy_servers + 1))
    fi
  done
fi

# Color based on server health
if [ "$unhealthy_servers" -gt 0 ]; then
  color="\033[33m"  # Yellow - some servers unhealthy
  icon="⚠️"
elif [ "$server_count" -gt 0 ]; then
  color="\033[32m"  # Green - all servers healthy
  icon="🔌"
else
  color="\033[90m"  # Gray - no servers
  icon="⚫"
fi

server_names=$(echo "$mcp_servers" | jq -r '.[].name // empty' 2>/dev/null | tr '\n' ',' | sed 's/,$//')
if [ -n "$server_names" ] && [ ${#server_names} -gt 30 ]; then
  server_names="${server_names:0:27}..."
fi

RESET="\033[0m"

if [ "$server_count" -gt 0 ]; then
  health_info=""
  if [ "$unhealthy_servers" -gt 0 ]; then
    health_info=" (${unhealthy_servers} unhealthy)"
  fi

  if [ -n "$server_names" ]; then
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers${health_info} │ ${active_tools} tools │ ${server_names}"
  else
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers${health_info} │ ${active_tools} tools"
  fi
else
  echo -e "${icon} MCP ${color}disconnected${RESET}"
fi

MCP Server Status Monitor with Tool Categories

Version grouping tools by category for better organization

#!/usr/bin/env bash

# MCP Server Status Monitor with Tool Categories

input=$(cat)

mcp_servers=$(echo "$input" | jq -r '.mcp.servers // []' 2>/dev/null || echo "[]")
server_count=$(echo "$mcp_servers" | jq 'length' 2>/dev/null || echo "0")

active_tools=0
declare -A tool_categories

if [ "$server_count" -gt 0 ]; then
  for server in $(echo "$mcp_servers" | jq -r '.[] | @base64'); do
    decoded=$(echo "$server" | base64 -d 2>/dev/null || echo "{}")
    tools=$(echo "$decoded" | jq '.tools | length // 0' 2>/dev/null || echo "0")
    server_name=$(echo "$decoded" | jq -r '.name // "unknown"' 2>/dev/null || echo "unknown")

    active_tools=$((active_tools + tools))

    # Categorize by server name prefix
    if [[ "$server_name" == *"filesystem"* ]] || [[ "$server_name" == *"file"* ]]; then
      tool_categories["filesystem"]=1
    elif [[ "$server_name" == *"git"* ]]; then
      tool_categories["git"]=1
    elif [[ "$server_name" == *"database"* ]] || [[ "$server_name" == *"db"* ]]; then
      tool_categories["database"]=1
    fi
  done
fi

if [ "$server_count" -gt 0 ]; then
  color="\033[32m"
  icon="🔌"
else
  color="\033[90m"
  icon="⚫"
fi

categories_list=""
for category in "${!tool_categories[@]}"; do
  if [ -z "$categories_list" ]; then
    categories_list="$category"
  else
    categories_list="$categories_list,$category"
  fi
done

server_names=$(echo "$mcp_servers" | jq -r '.[].name // empty' 2>/dev/null | tr '\n' ',' | sed 's/,$//')
if [ -n "$server_names" ] && [ ${#server_names} -gt 30 ]; then
  server_names="${server_names:0:27}..."
fi

RESET="\033[0m"

if [ "$server_count" -gt 0 ]; then
  if [ -n "$categories_list" ]; then
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers │ ${active_tools} tools │ ${categories_list}"
  elif [ -n "$server_names" ]; then
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers │ ${active_tools} tools │ ${server_names}"
  else
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers │ ${active_tools} tools"
  fi
else
  echo -e "${icon} MCP ${color}disconnected${RESET}"
fi

MCP Server Status Monitor Installation Example

Complete setup script with MCP configuration verification

#!/bin/bash
# Installation script for MCP Server Status Monitor

# Check for jq (required for JSON parsing)
if ! command -v jq &> /dev/null; then
    echo "Installing jq for JSON parsing..."
    if [[ "$OSTYPE" == "darwin"* ]]; then
        brew install jq
    elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
        sudo apt-get install -y jq || sudo yum install -y jq
    else
        echo "Please install jq manually: https://stedolan.github.io/jq/"
    fi
fi

# Check for base64 (usually available, but verify)
if ! command -v base64 &> /dev/null; then
    echo "Warning: base64 command not found. Script may not work correctly."
    echo "Install base64: macOS (usually pre-installed), Linux (coreutils package)"
fi

# Check MCP configuration
if [ -f ~/.mcp.json ]; then
    echo "MCP configuration found: ~/.mcp.json"
    echo "Verifying configuration..."
    if jq empty ~/.mcp.json 2>/dev/null; then
        echo "MCP configuration is valid JSON"
    else
        echo "Warning: MCP configuration may be invalid JSON"
    fi
else
    echo "Note: MCP configuration not found at ~/.mcp.json"
    echo "MCP servers can be configured in ~/.mcp.json or via 'claude mcp add' command"
fi

# Test Unicode characters
if echo -e '🔌 ⚫ ⚠️' &> /dev/null; then
    echo "Unicode characters supported"
else
    echo "Warning: Unicode characters may not be supported in your terminal"
fi

mkdir -p .claude/statuslines

cat > .claude/statuslines/mcp-server-status-monitor.sh << 'SCRIPT_EOF'
#!/usr/bin/env bash

# MCP Server Status Monitor
# Shows connected MCP servers and active tools

read -r input

mcp_servers=$(echo "$input" | jq -r '.mcp.servers // []' 2>/dev/null || echo "[]")
server_count=$(echo "$mcp_servers" | jq 'length' 2>/dev/null || echo "0")

active_tools=0
if [ "$server_count" -gt 0 ]; then
  for server in $(echo "$mcp_servers" | jq -r '.[] | @base64'); do
    decoded=$(echo "$server" | base64 -d 2>/dev/null || echo "{}")
    tools=$(echo "$decoded" | jq '.tools | length // 0' 2>/dev/null || echo "0")
    active_tools=$((active_tools + tools))
  done
fi

if [ "$server_count" -gt 0 ]; then
  color="\033[32m"
  icon="🔌"
else
  color="\033[90m"
  icon="⚫"
fi

server_names=$(echo "$mcp_servers" | jq -r '.[].name // empty' 2>/dev/null | tr '\n' ',' | sed 's/,$//')
if [ -n "$server_names" ] && [ ${#server_names} -gt 30 ]; then
  server_names="${server_names:0:27}..."
fi

RESET="\033[0m"

if [ "$server_count" -gt 0 ]; then
  if [ -n "$server_names" ]; then
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers │ ${active_tools} tools │ ${server_names}"
  else
    echo -e "${icon} MCP ${color}${server_count}${RESET} servers │ ${active_tools} tools"
  fi
else
  echo -e "${icon} MCP ${color}disconnected${RESET}"
fi
SCRIPT_EOF

chmod +x .claude/statuslines/mcp-server-status-monitor.sh

# Add to settings.json
if [ ! -f .claude/settings.json ]; then
    echo '{"statusLine":{"type":"command","command":"$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-server-status-monitor.sh","refreshInterval":2000}}' > .claude/settings.json
else
    jq '.statusLine = {"type":"command","command":"$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-server-status-monitor.sh","refreshInterval":2000}' .claude/settings.json > .claude/settings.json.tmp
    mv .claude/settings.json.tmp .claude/settings.json
fi

echo "MCP Server Status Monitor installed successfully!"
echo "Note: MCP server status requires Claude Code to expose MCP context in statusline JSON"
echo "Verify MCP servers: claude mcp list"
echo "Add MCP server: claude mcp add --transport stdio server-name command"

Troubleshooting

Statusline shows 'MCP disconnected' despite configured servers

Verify servers are actually connected: run 'claude mcp list' to check server status. Ensure servers are properly configured in ~/.mcp.json and restart Claude Code if needed. Check MCP context is available in statusline JSON: echo '$input' | jq .mcp. Verify Claude Code version supports MCP statusline API. Check server startup logs for errors.

Server count shows 0 but MCP servers are running in terminal

Check that MCP context data is accessible. Verify Claude Code version supports MCP statusline API. Run 'claude mcp get [server-name]' to verify individual server status. Check if MCP context is exposed in statusline JSON: echo '$input' | jq .mcp.servers. Ensure servers are registered with Claude Code, not just running externally. Restart Claude Code to refresh MCP connections.

Tool count incorrect or not updating

This indicates silent tool registration failure. Run '/mcp' in Claude Code to verify tool registration. Restart connected servers if tools remain unavailable despite connection. Check tool count calculation: for each server, verify tools array exists. Verify base64 decoding works: echo 'test' | base64 | base64 -d. Check jq parsing: echo '$input' | jq '.mcp.servers[0].tools | length'.

MCP server startup failures or connection timeouts

Launch with --mcp-debug flag. Check logs: ~/Library/Logs/Claude/mcp.log (macOS) or ~/.local/share/claude/mcp.log (Linux). Verify server.connect() is called and transport listener is active. Check server configuration in ~/.mcp.json. Verify server command is executable: which [server-command]. Test server manually: [server-command] --help.

JSON-RPC errors like 'Method not found' or invalid JSON

Server may not support prompts/list or resources/list, or writes non-JSON to stdout. Ensure JSON-RPC 2.0 compliance. Use MCP Inspector for interactive testing. Check server implementation follows MCP protocol. Verify server stdout/stderr separation. Check for error messages in server logs.

Server names not displaying or showing as empty

Verify server name extraction: echo '$input' | jq '.mcp.servers[].name'. Check server name field exists in MCP context. Verify jq parsing works: echo '$input' | jq '.mcp.servers | length'. Check string truncation logic if names are too long. Verify tr and sed commands work: echo 'test\ntest' | tr '\n' ',' | sed 's/,$//'.

Base64 decoding errors or script failures

Verify base64 command is available: which base64. Test base64 encoding/decoding: echo 'test' | base64 | base64 -d (should return 'test'). Check base64 -d flag syntax (may vary by OS). Verify jq @base64 encoding works: echo '[{"name":"test"}]' | jq -r '.[] | @base64'. Add error handling for base64 decode failures.

Statusline not updating or stuck at 'disconnected'

Check JSON input is being read: echo '$input' | jq .. Verify mcp.servers field exists: echo '$input' | jq .mcp.servers. Check jq is installed: which jq. Verify MCP context is available in Claude Code statusline JSON (may require Claude Code version with MCP support). Check refreshInterval in settings.json is set to 2000ms or lower. Restart Claude Code to refresh MCP connections.

Source citations

Add this badge to your README

Show that MCP Server Status Monitor - Statuslines is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/statuslines/mcp-server-status-monitor.svg)](https://heyclau.de/entry/statuslines/mcp-server-status-monitor)

How it compares

MCP Server Status Monitor - Statuslines side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Real-time MCP server monitoring statusline showing connected servers, active tools, and performance metrics for Claude Code MCP integration

Open dossier

A Claude Code statusline that reads the session JSON on stdin and splits total_duration_ms into API processing time versus network/waiting time (total minus API).

Open dossier

Real-time burn rate monitor showing cost per minute, tokens per minute, and projected daily spend to prevent budget overruns during Claude Code sessions.

Open dossier

Multi-provider AI performance dashboard with context occupancy tracking, truncation warnings, TTFT latency, tokens/min rate, and model comparison metrics.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitter
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Brand
Categorystatuslinesstatuslinesstatuslinesstatuslines
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorJSONboredJSONboredJSONboredJSONbored
Added2025-10-162025-10-252025-10-252025-10-23
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Source repo
Safety notesRuns 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.Configured as a command-type statusline, so the script runs automatically on every status update. The Examples "Installation" script writes .claude/statuslines/api-latency-breakdown.sh and edits .claude/settings.json, and runs brew/apt-get/yum to install bc.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.
Privacy notesReads 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.The Examples "Enhanced P95" variant appends every measured network time to /tmp/claude_latency_history.txt, leaving session timing data on disk until manually cleared.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, context occupancy) and renders it in the local terminal; it does not send data off-machine.
Prerequisites
  • Claude Code CLI installed and configured with MCP support
  • Bash shell available (bash 4.0+ recommended for associative arrays and string manipulation)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • base64 command (usually pre-installed, required for base64 encoding/decoding of server data)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • bc calculator (bc 1.07+ recommended for floating point calculations, optional - script falls back to integer math)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • bc calculator (bc 1.07+ required for floating point calculations - script will fail without bc)
  • Claude Code CLI installed and configured
  • Bash shell available (bash 4.0+ recommended for arithmetic operations)
  • jq command-line JSON processor (jq 1.6+ recommended for safe extraction with // defaults)
  • date command with epoch conversion support (macOS: -j flag, Linux: -d flag)
Install
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-server-status-monitor.sh",
    "refreshInterval": 2000
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/api-latency-breakdown.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/burn-rate-monitor.sh",
    "refreshInterval": 500
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/ai-model-performance-dashboard.sh"
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.