you › track my time with Claude
Automatic time tracking
for Claude.
Anthropic’s assistant — on the web, desktop, mobile, and in the terminal as Claude Code. Connect it to Temporal.ist over MCP and Claude becomes your time tracker: start timers, log hours, fix entries, pull reports and send invoices — by saying so. Underneath, automatic time tracking keeps capturing your work from file changes and URLs. No screenshots, ever.
you ›
you › set it up
Time tracking using Claude, in one minute
On claude.ai, add Temporalist as a custom connector; in Claude Code it’s one command. Both use the same login as your dashboard.
claude mcp add --transport http --scope user temporalist https://temporal.ist/mcphttps://temporal.ist/mcpSign-in is the same OAuth login as your dashboard — revocable anytime. Full per-client details live on the AI time tracking page.
you › what do I say?
Claude time tracking, in plain language
- “Create a project called Dunder Mifflin and start a timer.”
- “Add 3 hours to Dunder Mifflin yesterday — researching deployment.”
- “How much time did I spend on client work this week?”
- “Move this morning's entry to the right project.”
- “Stop the timer — actually, I stopped at 17:00.”
Nineteen tools cover the whole workflow — timers, backdated time logging, corrections, typo-tolerant project lookup, pause-aware reports in your timezone. Every session Claude creates is labeled in your dashboard, so you always see which hours came from AI time logging and which from automatic tracking.
you › invoice it
Claude invoicing: from tracked hours to a sent invoice
“Invoice Dunder Mifflin for July.” Temporalist gathers the unbilled sessions, builds a draft with line items per project — pause-aware hours times your rates, rounded up per your billing defaults — and hands Claude a link for you to review. Only after you explicitly confirm does the invoice get emailed to your client. Billing and customer data are extra secured behind their own off-by-default setting, so nothing sensitive moves until you allow it.
you › a few questions
FAQ
How does time tracking using Claude work?
Temporal.ist runs a remote MCP server at https://temporal.ist/mcp. You connect Claude (claude.ai & Claude Code) once, sign in, and from then on you talk: “start a timer for Dunder Mifflin”, “add 3 hours yesterday”, “how much time did I spend this week?”. Claude calls the right tool and the result lands in your Temporalist ledger — the same one the automatic tracker fills from file changes and URLs.
Is this automatic time tracking for Claude, or manual?
Both halves are covered. The Temporalist desktop app and browser extension track automatically — file saves and URLs become sessions without timers or screenshots. Claude adds the conversational half: backdated time logging, corrections, questions and invoicing for everything automation can't see.
Can I do Claude invoicing — turn tracked hours into an invoice?
Yes. Ask Claude to invoice a client and Temporalist builds a draft from your unbilled sessions — line items per project, pause-aware hours times your rates, with your round-up rules applied. Nothing is emailed until you explicitly confirm, and invoicing requires the sensitive-data opt-in in your settings.
Does this work in Claude Code as well as claude.ai?
Yes. The connector follows your Claude account to web, desktop and mobile, and Claude Code connects with a single `claude mcp add` command. Both talk to the same Temporalist account, so a timer started in Claude Code is visible when you ask claude.ai about your week.
What does Claude time tracking cost?
Temporal.ist is free to start — automatic tracking included. The MCP connection for Claude (and every other assistant) is part of Temporalist Pro; one subscription covers all your connected clients.