timer_start — time tracker timesheet billable hours MCP Tool
timer_start
(timer start) is one of 14 tools on the
time tracker timesheet billable hours
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call timer_start from your client
- Claude Code time tracker timesheet billable hours timer_start run in your project directory
- Claude Desktop time tracker timesheet billable hours timer_start ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor time tracker timesheet billable hours timer_start ~/.cursor/mcp.json
- VS Code time tracker timesheet billable hours timer_start .vscode/mcp.json
- Zed time tracker timesheet billable hours timer_start ~/.config/zed/settings.json
- Windsurf time tracker timesheet billable hours timer_start ~/.codeium/windsurf/mcp_config.json
- Cline time tracker timesheet billable hours timer_start ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI time tracker timesheet billable hours timer_start ~/.gemini/settings.json
- Grok time tracker timesheet billable hours timer_start .mcp.json (in your project root)
- ChatGPT time tracker timesheet billable hours timer_start Settings → Connectors → Advanced → Developer mode
- Claude.ai time tracker timesheet billable hours timer_start Settings → Connectors → Add custom connector
- LangChain time tracker timesheet billable hours timer_start pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http time-tracker-timesheet-billable-hours https://mcp.zovo.one/mcp/time-trackerOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.