openclaw-usage-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@openclaw-usage-mcpshow my usage costs for this week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
openclaw-usage-mcp
MCP server that reads local OpenClaw session files for usage and cost data. No network calls or authentication required — it scans the JSONL session files directly from disk.
AI Agent ──stdio──▶ MCP Server ──reads──▶ ~/.openclaw/agents/*/sessions/*.jsonlTools
Tool | Description |
| Token counts and costs for a date range, broken down by period and model |
| Sessions with usage breakdown, grouped by period (top-N or all) |
| Per-message logs for a session: timestamps, token counts, costs, roles |
Related MCP server: nikhilnt
Setup
1. Install dependencies
pip install mcp2. Configure
The server reads these environment variables:
Variable | Default | Description |
|
| Path to the OpenClaw agents directory containing session files |
3. Register with your MCP client
mcporter (recommended with OpenClaw):
mcporter config add usage \
--command python3 \
--arg /path/to/server.py \
--scope homeClaude Code (~/.claude/settings.json):
{
"mcpServers": {
"openclaw-usage": {
"command": "python3",
"args": ["/path/to/server.py"]
}
}
}How it works
The server scans JSONL session files from the OpenClaw agents directory:
Active sessions:
~/.openclaw/agents/*/sessions/*.jsonlArchived (reset) sessions:
~/.openclaw/agents/*/sessions/*.jsonl.reset.*
Each session file contains JSON lines with type: "session" headers, type: "message" entries (with usage/cost data on assistant messages), and type: "model_change" entries for model switches.
The server aggregates token counts and costs per model, per session, and per time period — returning the same structured output format the tools have always used.
Archived .reset.* files are included in scans, so usage from reset sessions is no longer invisible.
Running standalone
python3 server.pyCommunicates over stdio using the MCP protocol.
Previous architecture
Earlier versions used the gateway's WebSocket RPC API with Ed25519 device
authentication. That code (including device_auth.py) is preserved at tag
v0.1.0-gateway-api.
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP server for LLM cost estimation, model comparison, and budget-aware routing.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Analytics for MCP servers. Query your tool calls, first-call success, retries and schema cost.
Related MCP Servers
- AlicenseAqualityAmaintenanceLocal-first dashboard + MCP server that parses Claude Code and Codex JSONL files into a SQLite cost / token tracker. Per-MCP and per-tool breakdown, session drill-down, dedup by request_id; never talks to vendor APIs5100 npm1MIT
- AlicenseBqualityFmaintenanceTrack LLM token costs across Claude, GPT and Gemini. MCP server + CLI with optimization hints and $ savings estimates.88 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for querying OpenAI usage and cost data, including spend summaries, daily breakdowns, month-over-month comparisons, and token usage by model.3MIT
- AlicenseAqualityBmaintenanceA read-only MCP server that exposes local coding-agent session logs as three tools for introspection of recent work, debugging tool failures, and tracking token usage and estimated cost without parsing log files.3MIT