Wick MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WICK_WS_PORT | No | Port for WebSocket live updates (default: 6790) | 6790 |
| WICK_NO_WATCH | No | Set to '1' to disable the Claude Code log watcher | |
| WICK_HTTP_PORT | No | Port for HTTP dashboard (default: 6789) | 6789 |
| WICK_CLAUDE_PROJECTS | No | Custom path to Claude projects log directory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wick_trackA | Track token usage for this response. Call this after EVERY Claude response automatically. Wick uses this to compute your live burn rate, session cost, and estimated messages remaining. |
| wick_statusA | Get your current Claude session stats — tokens used, cost in USD and INR, burn rate, and messages left estimate. |
| wick_resetA | Reset the session counter. Use when starting a new task or after a rate limit reset. |
| wick_exportA | Export your session data as JSON, CSV, or a Markdown table. |
| wick_summaryB | All-time usage summary across every Wick session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: track records usage, status shows current session stats, reset clears the counter, export outputs data, and summary provides all-time totals. There is no ambiguity between them as the descriptions are explicitly differentiated.
All tool names follow a consistent 'wick_' prefix and use lowercase single-word names. However, the second part mixes verbs (track, reset, export) with nouns (status, summary), deviating slightly from a verb_noun pattern, but the overall style is uniform and predictable.
With 5 tools, the server is well-scoped for its purpose of token usage tracking. Each tool serves a necessary function without redundancy, and the count is within the ideal 3-15 range.
The tool set covers the full lifecycle of usage tracking: recording (track), viewing current status (status), resetting sessions (reset), exporting data (export), and summarizing all-time usage (summary). There are no obvious gaps for this domain.