Does Cursor support the Wakatime MCP server?

Yes. Cursor connects to the Wakatime MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.

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

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

Which Wakatime tools can Cursor 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 Cursor?

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

What if Cursor doesn't show Wakatime tools?

Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.

Connect Wakatime to Cursor (MCP setup guide)

Ask Cursor to use the get machines tool in Wakatime
Ask Cursor to use the get coding summaries tool in Wakatime
Ask Cursor to use the get insights tool in Wakatime
Ask Cursor to use the manage data exports tool in Wakatime
Ask Cursor to use the get goals 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 Metorial to your MCP config
Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
```
{
  "mcpServers": {
    "metorial": {
      "url": "<your-magic-mcp-url>"
    }
  }
}
```
3. Sign in
Open Customize in the sidebar, find Metorial and sign in to load Wakatime tools.

Once Wakatime is enabled in Metorial, teammates sign in with SSO and get the same connection in Cursor, 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.

Cursor picks MCP tools automatically when they are relevant, including in Plan Mode. Name a Wakatime tool to steer it.
Cursor asks for approval before it uses an MCP tool by default. Click the arrow next to the tool name to check the arguments first.
Switch the Metorial server off from Customize in the sidebar without removing it.
Cursor shows each Wakatime tool response in chat, with expandable views of the arguments and the result.

Metorial connects but tools are missing or failing: Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.
Your company blocks the server: Enterprise admins approve remote servers in Team Settings, then MCP Configuration. Ask them to add a URL entry for your Metorial URL.
Cursor asks before every tool call: That is the default. Allowlist the Metorial tools you trust in your Run Mode settings to run them without a prompt.

Based on the Cursor MCP documentation.

Frequently asked questions

Common questions about connecting Wakatime to AI agents with Metorial.

Does Cursor support the Wakatime MCP server?
Yes. Cursor connects to the Wakatime MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.
Do I need an API key to connect Wakatime to Cursor?
No. You sign in to Wakatime once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.
Which Wakatime tools can Cursor 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 Cursor?
Yes. Role-based access control decides who can use Wakatime and which of its tools appear in Cursor, and every call is logged with the person's identity.
What if Cursor doesn't show Wakatime tools?
Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.