For AI Developers

The only time tracker your AI coding tool controls.

ClockMe runs as a remote MCP server. Add it to Claude Code, Cursor, Windsurf, Copilot, or Gemini CLI — and your timer starts automatically every session. No plugins, no manual clicks.

Connect your AI tools freeView integrations

The problem with time tracking for ai developers

✗

AI sessions are long and hard to track

A Claude Code session can run three hours before you come up for air. By then, the timer context is gone. You end up billing a rough estimate that is probably low.

✗

Existing tools do not understand AI workflows

Time trackers built five years ago have no concept of an AI coding session. They have no hooks, no MCP, no way to integrate with the tools where you actually work.

✗

Context switching kills accuracy

You jump between five AI sessions, browser research, and client calls. Each context switch is a manual timer stop-and-start you probably forget. Hours leak out constantly.

How ClockMe solves it

Built for the way ai developers actually work.

Unique

Remote MCP server — 18 tools

ClockMe exposes a full MCP server at https://clockme.co/api/mcp. Add one URL to any AI coding tool and you get 18 timer tools: start, stop, list entries, get reports, manage projects, and more.

Claude Code

SessionStart hook — zero clicks per session

Claude Code supports shell hooks that fire on session open and close. ClockMe uses this to auto-start a timer the moment a session opens and stop it when you exit. Completely invisible in normal use.

Ask your AI to manage time

In any MCP-connected tool: 'start a timer on the client portal project', 'how many hours have I logged this week?', 'switch timer to the API project'. Natural language, no context switch.

Works with every major AI coding tool

Claude Code, Cursor, Windsurf, GitHub Copilot (VS Code 1.102+), Gemini CLI — all use the same ClockMe API key and MCP endpoint. One account, all tools, unified dashboard.

Works with your AI tools

One API key. One MCP endpoint. Every AI coding tool you already use.

Claude CodeHook-based auto-start — zero clicks. The flagship integration.Setup guide →CursorComposer agent MCP — natural language timer controlSetup guide →WindsurfCascade MCP — HTTP remote with Bearer tokenSetup guide →GitHub CopilotVS Code 1.102+ agent mode MCPSetup guide →Gemini CLITerminal-based remote MCP — SSH compatibleSetup guide →

All integrations use the same API key. Manage everything from one dashboard. Use the Setup Wizard →

Questions from ai developers

What is MCP and why does it matter for time tracking?

MCP (Model Context Protocol) is an open standard that lets AI tools call external services as tools. ClockMe exposes 18 timer tools over MCP — so Claude Code, Cursor, and others can start, stop, and query timers directly. No browser tab switching needed.

Does the Claude Code hook work in every project folder?

Yes. The hook lives in your global ~/.claude/settings.json so it fires for every Claude Code session, regardless of which folder you open. The timer logs to whichever project you configured in the hook command.

Can I switch which project the auto-timer logs to?

Yes. Once inside a session, tell ClockMe via MCP: 'switch timer to the [project name] project'. ClockMe stops the current entry and starts a new one on the new project. No settings edit needed.

How many MCP tools does ClockMe expose?

18 tools: clockme_status, clockme_start_timer, clockme_stop_timer, clockme_update_timer, clockme_list_entries, clockme_log_time, clockme_get_report, clockme_list_projects, clockme_get_project, clockme_list_tasks, clockme_get_budget, clockme_edit_entry, and more.

Is ClockMe free for developers?

Yes. ClockMe is free for individual users with all features included — MCP, hooks, invoicing, concurrent timers, reports. A team Pro plan is coming at $8/seat/month for shared workspaces.

Ready to stop losing hours?

Free for individuals. Takes 5 minutes to connect your first AI tool.

Connect your AI tools free