Home · Setup · Claude.ai and Claude Desktop connectors

MCP Time Tracker in Claude.ai and Claude Desktop connectors

Track billable time without leaving the chat. It keeps a running timer, takes time you forgot to log, applies an hourly rate per project, and turns the log into a report, a CSV or invoice lines. Plain JSON on disk.

This is the client with no terminal and no filesystem of its own, so the free tier's history window matters more here than anywhere else: a report is read in the chat, not exported to a file you would open elsewhere.

What you get

You sayTool
Start a timer for the Acme website project.timer_start
Log 2.5 hours yesterday for Acme, design review, at 90 euros an hour.entry_add
How many hours did I bill this month, grouped by project?report

In the audit run each of those sentences took one tool call, at 7.7 s and 14.6 s including a turn that also logged an expense.

Connect it, no install

https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/time-tracker/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.

  1. Open https://mcp.zovo.one/mcp/connect and copy the URL printed for MCP Time Tracker.
  2. There is no config file here: the Add custom connector form asks for a name and a Remote MCP server URL, with an Advanced settings section for an optional OAuth Client ID and Client Secret.
  3. Paste the URL as the Remote MCP server URL. Leave the optional OAuth Client ID and Client Secret blank; this endpoint does not use them.
  4. Click Connect, then turn the connector on for a conversation from the + button, Connectors.

Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Time Tracker generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.

Claude.ai and Claude Desktop connectors notes worth knowing first

On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.

Free: unlimited timers and entries, 7 days of reports, 2 rated projects. Pro is $19 once, verified offline, and binds to the token after checkout.

Questions

Does this need OAuth?

No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.

I am on a Team or Enterprise plan and cannot add a connector.

That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.

Can I use my Pro key instead of the free anonymous token?

Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Time Tracker for that connector.

Why did a generated file come back as a link instead of opening?

The connector runs server-side with no filesystem of its own, so any file MCP Time Tracker produces is handed back as a download link that expires after one hour, rather than a path on disk.

Related

MCP Time Tracker in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs