What WakaTime scopes does Lyro need?

It depends on what you ask for: Get User Summaries requires the read_summaries scope and List Goals requires read_goals. Generate WakaTime OAuth Authorize URL produces the consent link a user is sent to, so what Lyro can read afterwards is exactly what was granted at that screen and nothing more.

Can Lyro log or correct coding time?

No. Every action here reads - stats, summaries, goals, insights, projects, machines, leaderboards, and plugin metadata. Coding time is recorded by the WakaTime plugins in your editors, and Lyro reports on that record rather than writing to it.

Can Lyro report on someone other than the connected account?

Get User Details and List User Projects both take a user ID or username, with 'current' standing in for the authenticated user, and List Leaders ranks public users by activity. What is actually visible follows each user's WakaTime privacy settings, which Get User Details returns alongside their plan.

How does Lyro spot a machine that stopped reporting?

List User Agents returns the plugins and editors that have actually sent data for a user, and List Machine Names returns each machine with its last seen time. A machine that stops appearing is a plugin that has stopped sending, which is the usual cause of an unexpectedly quiet day.

Wakatime MCP integration

Reports today's coding total, compares date ranges by language and editor, tracks goal progress, and flags machines that stopped reporting.

Connect Wakatime See all integrations

17actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get user details
Lyro retrieves detailed profile information for a WakaTime user. Support teams access account details to assist users with setup and subscriptions.
Get user stats
Lyro compiles coding statistics for a user over the default time range. Developers understand their productivity patterns instantly.
List user projects
Lyro enumerates all WakaTime projects associated with a specified user. Teams track which projects are being monitored without manual queries.

See all 17 actions

How businesses use Wakatime + Lyro

Each card is one request a support team gets, and the Wakatime actions Lyro runs to close it.

Answer how much was coded today
Lyro pulls the same today view an IDE status bar shows, broken down by project, language, and editor, and reads the daily summaries either side of it for context.
Get Current User's Status Bar SummaryGet User SummariesGet User Stats
Break a date range down by language and project
Lyro returns stats for a specific range with breakdowns by language, editor, project, and operating system, plus daily averages and the best day inside it.
Get User Stats by RangeList User ProjectsGet User Insight
Track a goal or a lifetime total
Lyro reads the goals set on an account with their progress series, returns total coding time since the account was created, and reports the profile and timezone the numbers are calculated in.
List GoalsGet User's Total Time Since CreationGet User Details
Compare against the wider WakaTime population
Lyro pulls aggregate statistics across all WakaTime users for a time range, the public leaderboard filtered by language or country, and the full list of tracked languages.
Get Aggregate StatsList LeadersList Program Languages

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Wakatime actions it has and picks the ones a request needs.

01
Connect Wakatime
Authorize the Wakatime account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Wakatime actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Wakatime · Lyro

Everything else about Wakatime

Setup, permissions, and the limits of what Lyro can do inside Wakatime.

It depends on what you ask for: Get User Summaries requires the read_summaries scope and List Goals requires read_goals. Generate WakaTime OAuth Authorize URL produces the consent link a user is sent to, so what Lyro can read afterwards is exactly what was granted at that screen and nothing more.

Every action available in Wakatime

All 17 actions your agent can call on Wakatime, straight from the live MCP connection.

Get aggregate stats
Retrieve aggregate coding statistics across all WakaTime users for a given time range.
Get current user's status bar summary for today
Get current user's coding activity today for displaying in IDE status bars.
List ide plugins
List WakaTime IDE plugins with metadata.
List goals
List a user's goals with progress series and metadata.
Get user insight
Retrieve an insight for a user over a time range.
List leaders
List public leaders ranked by coding activity.
List machine names
List a user's machines including last seen time.
Get API meta information
Retrieve WakaTime API meta information, including public IP addresses used by WakaTime servers.
Generate wakatime oauth authorize URL
Generate OAuth 2.0 authorization URL.
Get user details
Get detailed profile information for a WakaTime user by user ID or username.
Get user's total time since creation
Retrieve total coding time since account creation for a user.
Get user stats
Retrieve coding statistics for a user over the default time range.
Get user stats by range
Retrieve comprehensive coding statistics for a user over a specific time range.
Get user summaries
Get user's coding activity for a time range as daily summaries.
List program languages
List all verified program languages supported by WakaTime.
List user projects
List WakaTime projects for a specified user.
List user agents
List plugins and editors which have sent data for a specified user.