token-meter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| usage_summaryA | Quick spend + token summary for Claude Code and Codex over a period. Reads local Token Meter data; never touches vendor APIs. |
| recent_sessionsA | List Claude Code / Codex sessions with activity in the recent window — useful when you accidentally closed a terminal and want to resume. To resume: cd into the project dir and run |
| session_toolsA | Show which MCP servers / built-in tools a given session used, with call counts, response sizes, and average latency. Helps debug "why was this session expensive/slow". |
| refresh_dataA | Re-scan ~/.claude/projects and ~/.codex/sessions to pick up new activity. Run this before other tools if you need up-to-the-minute numbers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| usage_summary | Summarize Claude Code + Codex usage for today / week / month. |
| recent_sessions | List recent Claude Code / Codex sessions with ready-to-paste resume commands. |
| session_tools | Show MCP / built-in tool breakdown for a specific session_id. |
| refresh_data | Re-scan local JSONL files to pick up new Claude Code / Codex activity. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/whdrnr2583-cmd/token-meter'
If you have feedback or need assistance with the MCP directory API, please join our Discord server