wakatime-mcp
Provides tools to retrieve daily summaries and today's summary from WakaTime, using the WakaTime Summaries API with an API key.
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., "@wakatime-mcp show my coding activity for today"
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.
๐ wakatime-mcp
An MCP server that exposes WakaTime summary tools over stdio. It proxies the WakaTime Summaries API with your API key and returns raw JSON for clients to parse as needed.
๐ Summary
Key features:
๐ Uses
WAKATIME_API_KEYfor authentication๐ Exposes daily summaries and todayโs summary
๐ฆ Runs via
npx(no install required)
Related MCP server: ATimeLogger MCP Server
๐ Quick Start (npx)
export WAKATIME_API_KEY="YOUR_API_KEY"
npx wakatime-mcp๐ค MCP Config (npx)
{
"command": "npx",
"args": ["-y", "github:geeknees/wakatime-mcp"],
"env": {
"WAKATIME_API_KEY": "YOUR_API_KEY"
}
}๐งฐ Available Tools
wakatime_summaries
{
"tool": "wakatime_summaries",
"arguments": {
"start": "2025-01-01",
"end": "2025-01-07",
"project": "my-project",
"timezone": "Asia/Tokyo"
}
}wakatime_today
{
"tool": "wakatime_today",
"arguments": {
"project": "my-project",
"timezone": "Asia/Tokyo"
}
}โ๏ธ Configuration
Environment Variable | Description | Required |
| WakaTime API key | โ |
๐งช Tests
npm testAvailable Tools
10 toolswakatime_all_time_since_todayA
Fetch processed all-time totals per project since the beginning of WakaTime tracking.
Inputs: project.
wakatime_durationsA
Fetch processed duration blocks by date/project/branches. Returns summarized time blocks, never raw API JSON.
Inputs: date, project, branches, timezone.
wakatime_heartbeatsA
Fetch processed heartbeat data for a date. Returns summarized counts by project/file, never raw heartbeat JSON.
Inputs: date, branch, project.
wakatime_mark_consumedA
Mark time ranges as consumed after a commit. Prevents double-counting in subsequent session_duration calls.
Inputs: file_paths (required), commit_hash (required), branch.
wakatime_projectsA
Fetch a processed list of available WakaTime projects with names and IDs.
Inputs: no named parameters.
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.
Inputs: project (required), since, branch.
wakatime_statsC
Fetch processed aggregated stats for a range (languages, editors, projects, daily average). Never raw API JSON.
Inputs: range, project, timezone.
wakatime_summariesB
WakaTime Summaries API ใๅฉใใๆๅฎๆ้ใฎๆฅๆฌกใตใใช(JSON)ใ่ฟใใพใใ
Inputs: end (required), start (required), project, branches, +1 more.
wakatime_todayB
ไปๆฅใฎใตใใช(JSON)ใ่ฟใใพใ๏ผAsia/Tokyo ใใใใฉใซใใซใใพใ๏ผใ
Inputs: project, timezone.
wakatime_userA
Validate the WakaTime API key and return account information.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
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.
Maintenance
Related MCP Connectors
Read your WakaTime coding time: summaries, stats, projects, goals, commits and leaderboards.
Query SEC EDGAR filings, XBRL financials, and company data via MCP. STDIO or Streamable HTTP.
Code::Stats MCP โ public user XP / activity.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to WakaTime coding analytics data through MCP tools. Enables querying coding stats, activity summaries, project lists, and time tracking information from your WakaTime account.MIT
- AlicenseAqualityCmaintenanceA standalone MCP server that exposes the ATimeLogger REST API to Claude Desktop/Code over stdio, enabling activity tracking (start/stop/pause/log), reports/history, and activity type management.8391 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying WakaTime coding activity data including summaries, stats, durations, and commits through an MCP server integrated with Pipeworx gateway.86 npmMIT

openrhyme-mcpofficial
AlicenseAqualityBmaintenanceEnables any MCP-compatible agent to query a local OpenRhyme activity timeline, search history, and issue control commands over stdio while keeping all data on-machine.51MIT