Claude Telemetry

MCP server for tracking Claude Code usage patterns, personal trends, and allowance limits

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "cordlesssteve-claude-telemetry-mcp": {
      "command": "node",
      "args": [
        "path/to/claude-telemetry-mcp/build/index.js"
      ]
    }
  }
}

Claude Telemetry MCP is a local server that tracks your Claude Code usage, analyzes trends, and monitors against allowance limits. It provides personal usage insights, proactive limit warnings, and productivity analytics to help you plan and optimize your workflow.

How to use

You use Claude Telemetry MCP by running the MCP server as part of your client setup and then querying it through your MCP client. The server exposes a set of tools you can call to retrieve current session metrics, daily/weekly usage, usage trends, and limit status, as well as analytics and insights to help you optimize your workflow. Use the provided tool endpoints to fetch data, receive proactive warnings when nearing limits, and project remaining capacity based on historical patterns.

How to install

Prerequisites: Node.js installed on your machine. You will also need npm to install the MCP package.

# Install the Claude Telemetry MCP package
npm install claude-telemetry-mcp

Configuration and usage steps

Add the MCP server configuration to your client setup so your MCP runtime can load and start the Claude Telemetry MCP server. The configuration below defines a single stdio-based server that runs locally using Node.js.

{
  "mcpServers": {
    "claude_telemetry": {
      "command": "node",
      "args": ["path/to/claude-telemetry-mcp/build/index.js"]
    }
  }
}

Using the MCP client to call tools

After you have the server started, use your MCP client to call the available tools. The server exposes functions to fetch current usage, today’s usage, week usage, usage summaries and trends, tool usage breakdowns, and health status. You can also monitor against limits and estimate remaining capacity.

Available tools

get_current_session_usage

Retrieve metrics for the current session including tokens consumed and activity duration.

get_today_usage

Get today’s usage summary and trends for quick daily awareness.

get_week_usage

Get weekly usage metrics and patterns to understand short-term trends.

get_usage_summary

Provide a comprehensive overview of your usage with personal insights.

get_usage_trends

Analyze usage patterns over a chosen period and optionally include predictions.

get_session_analytics

Analyze session patterns to reveal productivity and focus insights.

get_tool_usage_breakdown

Break down tool usage statistics and preferences.

check_usage_limits

Monitor usage against specified allowance limits and thresholds.

get_usage_warnings

Return threshold warnings and limit notifications.

estimate_remaining_capacity

Calculate remaining capacity based on current trends.

compare_usage_periods

Compare usage between different time periods for planning.

get_telemetry_health

Check the health and data quality of the telemetry system.