wakatime-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WAKATIME_API_KEY | Yes | WakaTime API key |
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 |
|---|---|
| wakatime_summariesB | WakaTime Summaries API を叩き、指定期間の日次サマリ(JSON)を返します。 |
| wakatime_todayB | 今日のサマリ(JSON)を返します（Asia/Tokyo をデフォルトにします）。 |
| wakatime_session_durationA | Fetch heartbeats, compute per-file coding time, subtract consumed ranges. Returns formatted summary like 'app.py 35m, auth.py 20m, total 55m'. No raw heartbeat data exposed. |
| wakatime_mark_consumedA | Mark time ranges as consumed after a commit. Prevents double-counting in subsequent session_duration calls. |
| wakatime_durationsA | Fetch processed duration blocks by date/project/branches. Returns summarized time blocks, never raw API JSON. |
| wakatime_projectsA | Fetch a processed list of available WakaTime projects with names and IDs. |
| wakatime_heartbeatsA | Fetch processed heartbeat data for a date. Returns summarized counts by project/file, never raw heartbeat JSON. |
| wakatime_all_time_since_todayA | Fetch processed all-time totals per project since the beginning of WakaTime tracking. |
| wakatime_statsC | Fetch processed aggregated stats for a range (languages, editors, projects, daily average). Never raw API JSON. |
| wakatime_userA | Validate the WakaTime API key and return account information. |
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 10 tools
Several tools (today, summaries, durations, heartbeats, stats) all return time-tracking data with overlapping periods and granularities, making selection potentially confusing. Descriptions clarify differences, but the boundaries between raw summaries, processed durations, and aggregated stats are not always obvious.
All tools share the wakatime_ prefix and use snake_case, creating a clear family identity. However, the semantic structure varies (e.g., wakatime_today is adverbial, wakatime_summaries is a plural noun, wakatime_mark_consumed is verb-object), so the pattern is consistent in style but not in syntactic form.
10 tools is a well-scoped number for a WakaTime integration, covering user info, projects, multiple time-reporting views, and a session-tracking workflow with mark_consumed. Each tool has a distinct role, and the count fits comfortably in the ideal 3-15 range.
The tool set covers the major WakaTime API areas: user validation, project listing, summaries, durations, heartbeats, stats, and all-time totals. The session_duration/mark_consumed pair adds a practical workflow. Missing advanced endpoints like goals or leaderboards are non-core, so the surface is nearly complete.