Exposes three MCP tools that parse your local Claude Code session logs to show token cost attribution. The analyze_claude_cost tool breaks down spend by output versus context re-sent every turn (typically 60%+ of bills), traces context growth across the session, and flags which models or tools are expensive. get_cost_benchmark compares your session against an offline reference dataset. tokenscope_share_summary generates privacy-safe markdown and SVG reports with no file paths or prompt content. Reads from ~/.claude/projects/**/*.jsonl, strictly local and read-only. Useful when an AI bill surprises you and you want the agent itself to explain where the money went, or when you're optimizing long-running sessions and need per-turn context metrics without leaving the chat.
claude mcp add --transport stdio wartzar-bee-tokenscope uvx tokenscope