How to connect WakaTime to OpenClaw
Connect WakaTime to OpenClaw with ClawLink: paste your WakaTime key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine.
WakaTimeAPI KEYMCPTrack coding time, language stats, and developer productivity. Once connected, OpenClaw can read and act on WakaTime from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to WakaTime access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical WakaTime setup: install one ClawHub skill, connect WakaTime in the browser, and OpenClaw can call real WakaTime actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the WakaTime skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "WakaTime" (hith3sh/wakatime) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/wakatime
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to WakaTime.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect WakaTime
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with WakaTime?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect WakaTime in the ClawLink dashboard — paste your WakaTime API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from WakaTime, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once WakaTime is connected in the dashboard, that agent calls the same 17 WakaTime tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
WakaTime MCP for OpenClaw
Looking for a WakaTime MCP server for OpenClaw? ClawLink connects WakaTime to OpenClaw and exposes 17 WakaTime tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes WakaTime integration works the same way.
What the OpenClaw WakaTime integration can do
17 WakaTime tools are ready for OpenClaw once the account is connected.
All 17 WakaTime tools for OpenClaw
| Tool | What it does |
|---|---|
Get aggregate stats wakatime_get_aggregate_stats | Retrieve aggregate coding statistics across all WakaTime users for a given time range |
Get current user status bar today wakatime_get_current_user_status_bar_today | Get current user's coding activity today for displaying in IDE status bars |
Get editors wakatime_get_editors | List WakaTime IDE plugins with metadata |
Get goals wakatime_get_goals | List a user's goals with progress series and metadata |
Get insights wakatime_get_insights | Retrieve an insight for a user over a time range |
Get leaders wakatime_get_leaders | List public leaders ranked by coding activity |
Get machine names wakatime_get_machine_names | List a user's machines including last seen time |
Get meta wakatime_get_meta | Retrieve WakaTime API meta information, including public IP addresses used by WakaTime servers |
Get oauth authorize wakatime_get_oauth_authorize | Generate OAuth 2.0 authorization URL |
Get user wakatime_get_user | Get detailed profile information for a WakaTime user by user ID or username |
Get user stats wakatime_get_user_stats | Retrieve coding statistics for a user over the default time range |
Get user stats by range wakatime_get_user_stats_by_range | Retrieve comprehensive coding statistics for a user over a specific time range |
Get user summaries wakatime_get_user_summaries | Get user's coding activity for a time range as daily summaries |
Get users all time since today wakatime_get_users_all_time_since_today | Retrieve total coding time since account creation for a user |
List program languages wakatime_list_program_languages | List all verified program languages supported by WakaTime |
List user projects wakatime_list_user_projects | List WakaTime projects for a specified user |
List user user agents wakatime_list_user_user_agents | List plugins and editors which have sent data for a specified user |
Try it: find the WakaTime tool you need
Browse the 17 WakaTime tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from WakaTime, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from WakaTime, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from WakaTime, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from WakaTime, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want WakaTime working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the WakaTime API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected WakaTime account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for WakaTime. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right WakaTime actions to the runtime in a format your agent can reliably use. | 17 tools for WakaTime are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes WakaTime to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect WakaTime in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the WakaTime key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the WakaTime skill but can't call the tools
The ClawHub skill teaches OpenClaw about WakaTime, but the calls run through the ClawLink plugin and your connected account. Make sure WakaTime is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect WakaTime from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling WakaTime tools
WakaTime tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every WakaTime call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
WakaTime returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for WakaTime has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw WakaTime integration?
Yes. ClawLink is the fastest way to connect OpenClaw to WakaTime: link your WakaTime account once in the browser and OpenClaw can call the WakaTime API through 17 ready-made tools — no custom code or token handling.
How do I add WakaTime to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink WakaTime skill from ClawHub, then you click Connect in the dashboard to authorize WakaTime. OpenClaw calls the tools from the next message — no config files, and the WakaTime key you paste is stored server-side instead of in your environment.
How long does it take to connect WakaTime to OpenClaw?
About two minutes. Sign in, click Connect next to WakaTime in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring WakaTime up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want WakaTime working from chat.
OpenClaw installed the WakaTime skill but can't call the tools
The ClawHub skill teaches OpenClaw about WakaTime, but the calls run through the ClawLink plugin and your connected account. Make sure WakaTime is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.