Does Claude support the Wakatime MCP server?

Yes. Claude connects to the Wakatime MCP server through its connector settings, pointed at your Metorial URL. You need any Claude plan; Free plans allow one custom connector.

Do I need an API key to connect Wakatime to Claude?

No. You sign in to Wakatime once through Metorial, and Claude uses that connection. No API keys go into Claude's settings.

Which Wakatime tools can Claude use?

All 20 Wakatime tools your team allows, such as List Projects, Get Project Commits, Delete Heartbeat. Admins can narrow that list per team.

Can I control which teammates use Wakatime in Claude?

Yes. Role-based access control decides who can use Wakatime and which of its tools appear in Claude, and every call is logged with the person's identity.

What if Claude doesn't show Wakatime tools?

On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.

Connect Wakatime to Claude (MCP setup guide)

Ask Claude to use the list projects tool in Wakatime
Ask Claude to use the get project commits tool in Wakatime
Ask Claude to use the delete heartbeat tool in Wakatime
Ask Claude to use the get user profile tool in Wakatime
Ask Claude to use the get heartbeats tool in Wakatime

1. Enable Wakatime in Metorial
In your Metorial portal, enable the Wakatime MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add a custom connector
Open Customize, then Connectors. Select Add, then Custom, then Web.
3. Paste your Metorial MCP URL
Name it Metorial, paste your Magic MCP URL (<your-magic-mcp-url>) and continue.
4. Sign in
Select Add and sign in to load Wakatime tools.

Once Wakatime is enabled in Metorial, teammates sign in with SSO and get the same connection in Claude, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

List Projects: List all coding projects that have recorded activity.
Get Project Commits: Retrieve commit history for a specific project with time-spent-coding data per commit.
Delete Heartbeat: Delete a specific heartbeat by its ID.
Get User Profile: Retrieve the current user's profile information including display name, email, timezone, last active plugin, social profiles, plan details, and machines.
Get Heartbeats: Retrieve raw coding activity events (heartbeats) for a specific day.
Get Private Leaderboards: List all private leaderboards the user has access to.
Create External Duration: Record activity durations from sources other than IDE plugins, such as calendar events, meetings, or code reviews.
Get Durations: Retrieve coding activity for a given day as time duration blocks.
Get Coding Stats: Retrieve aggregated coding statistics for a configurable time range.
Get Leaderboard: Access public or private leaderboards of users ranked by coding activity.
Get Machines: List all machines (computers) that have sent coding activity, including hostname, IP, and last seen time.
Get Coding Summaries: Retrieve coding activity summaries for a given date range, segmented by day.
Get Insights: Access deeper analytics about coding activity for a given time range.
Manage Data Exports: List existing data exports or request a new full data export of all coding activity.
Get Goals: Retrieve all coding goals.
And 5 more on the Wakatime MCP server page.

Turn Metorial on for a conversation with the + button, then Connectors; each connector has its own toggle.
Claude asks before it runs a Wakatime tool. Choose Allow always only for tools you trust to run unsupervised.
Use the Search and tools menu to switch off tools you do not need in the current conversation.
Remove the connector from Customize, then Connectors. Team and Enterprise owners can do this for the whole organization.

Members on a Team or Enterprise plan cannot add the connector: On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.
The Free plan only allows one custom connector: One is enough: your Metorial URL carries every app your team approves, so you never need a second connector.
Tools do not show up in a chat: Connectors are switched on per conversation. Open the + menu in the chat, choose Connectors, and turn Metorial on.

Based on the Claude MCP documentation.

Frequently asked questions

Common questions about connecting Wakatime to AI agents with Metorial.

Does Claude support the Wakatime MCP server?
Yes. Claude connects to the Wakatime MCP server through its connector settings, pointed at your Metorial URL. You need any Claude plan; Free plans allow one custom connector.
Do I need an API key to connect Wakatime to Claude?
No. You sign in to Wakatime once through Metorial, and Claude uses that connection. No API keys go into Claude's settings.
Which Wakatime tools can Claude use?
All 20 Wakatime tools your team allows, such as List Projects, Get Project Commits, Delete Heartbeat. Admins can narrow that list per team.
Can I control which teammates use Wakatime in Claude?
Yes. Role-based access control decides who can use Wakatime and which of its tools appear in Claude, and every call is logged with the person's identity.
What if Claude doesn't show Wakatime tools?
On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.